Develop Bugs

Nokia N1, wiped system, stuck on splash screen (Powered by Android) (Update!)

Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.

Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.

do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it

2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.

It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk

do you have full ROM for N1 tw or cn, if you have this can you share for me plêas

i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke

2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you

Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.

srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?

defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/

same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2

Help me please - something went haywire with unlocking bootloader.

I tried to follow directions here but in my haste and stupidity I may have followed incompatible directions.
Here's where I'm at. I have TWRP 3.0.2-M1 installed. I cannot install any system images and have them run (CM13 for example). I've tried unlocking my bootloader with no success.
I don't know what to do. I cannot load any images properly, but I am desperate to get things going. Am I totally screwed?
Would really, really appreciate direction. ZE551ML. I want the nightly CM13 image to run on my phone.
When I start my phone up, I get the Red Error that tells me my system isn't verified.
Please, please help.
EDIT: I have no OS installed.

You can boot into twrp.
Your bootloader is unlocked with the warning screen .
Do you know how to flash a Rom ?
What did you use to unlock ?
If you want people to help you need to describe what you used and why

timbernot said:
You can boot into twrp.
Your bootloader is unlocked with the warning screen .
Do you know how to flash a Rom ?
What did you use to unlock ?
If you want people to help you need to describe what you used and why
Click to expand...
Click to collapse
Yes, I tried to a flash a ROM but it keeps putting me back in the Recovery.
I used Giarmix's automatic tool to unlock and it said FAILED but I guess it worked once to get me TWRP.
I'm sorry, I'm trying to provide as much info as possible.

roach9 said:
Yes, I tried to a flash a ROM but it keeps putting me back in the Recovery.
I used Giarmix's automatic tool to unlock and it said FAILED but I guess it worked once to get me TWRP.
I'm sorry, I'm trying to provide as much info as possible.
Click to expand...
Click to collapse
Giovix modder tool ?
There is an option to return to stock.
Or gimme link to the one you used if not this one

timbernot said:
Giovix modder tool ?
There is an option to return to stock.
Or gimme link to the one you used if not this one
Click to expand...
Click to collapse
Yes, that one. Returning to stock doesn't work.
I also ran the following program in an attempt to get TWRP 3.0.2-M1 to install CM13:
M_BL_upgrade_for_zf2_551ml_6.0
After this, nothing works anymore.
EDIT: TWRP 3.0.2-M1 is installed, but when I go to install a ROM, I get an error:
When I try to wipe any partition, I get "ARGUMENT INVALID".
Sigh

You put the extracted folder in C/: of PC and run batch as admin?

timbernot said:
You put the extracted folder in C/: of PC and run batch as admin?
Click to expand...
Click to collapse
What extracted folder are you referring to?

Modder

timbernot said:
Modder
Click to expand...
Click to collapse
I have been running as admin and certain commands did work, but this is not. I erased my system/cache partitions in a panic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Is there a magic thing I can do within TWRP? **** I'm an idiot.

Can you fastboot flash stock recovery ?
Can you get into fastboot to flash stock recovery too ?

I flashed the newest stock recovery but it didn't work, I can only boot into my bootloader now.
I tried ASUS Flash Tool and it sees my device but it remains "Connected" and doesn't want to install the .raw file.

Wow just wow.
I'm going to bed lol

timbernot said:
Wow just wow.
I'm going to bed lol
Click to expand...
Click to collapse
Sigh.
I am an idiot. Thank you for trying ot help.

I will help later but need some rest

timbernot said:
I will help later but need some rest
Click to expand...
Click to collapse
I truly appreciate your time and assistance.

Okay, here's the issue I have.
When I install CM13 and GApps, it works fine. System patched unconditionally, success, etc.
When I reset my system, I get a red screen that says "Your device has failed verification and may not work properly. Go to www.g.co/ahg (just a guess)"
Then it boots back into my recovery, where normally, it should have gone to CM.
What gives? I have no idea what to do.
I tried to use the Asus Flash tool but it cannot install to my device.
I can still use fastboot.
I suspect that my problem is that I installed a MM Bootloader without rooting or without unlocking properly and it's not all effed.
I want to cry.
EDIT 2: I've spent all night doing this. I followed this:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But then I got caught up. xFSTK wasn't work so I unplugged my USB, BUT THEN IT STARTED RUNNING when it was unplugged?! But GET THIS. CM 13 RUNS.
But now when I turn on my phone, I get a weird line screen and I cannot boot into my Recovery OR my Bootloader. I can only load my ROM.
What the **** is going on?!?!?!?!?

Android version before bricking device?

CM 13, so Marshmallow.
Now the screen won't even turn on. This is ****ed.
EDIT: No screen at all. Nothing works. In boot cycle. Sending it to Asus and hopefully they fix this and send me it back. I'm never unlocking the bootloader or rooting, or doing anything to a phone ever ****ing again. This should not be that hard to do.

If u can boot cm then u can install recovery using adb
Download the latest recovery image file (.img) depending on which bootloader u have (MM/L).
Place it in the root of your /sdcard folder and rename it to twrp.img.
Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
Recoveries link http://theflamingskull.com/zenfone2.html

roach9 said:
CM 13, so Marshmallow.
Now the screen won't even turn on. This is ****ed.
EDIT: No screen at all. Nothing works. In boot cycle. Sending it to Asus and hopefully they fix this and send me it back. I'm never unlocking the bootloader or rooting, or doing anything to a phone ever ****ing again. This should not be that hard to do.
Click to expand...
Click to collapse
Wow and wow and more wow !
1)What firmware did you have on when you first used the modder ..........?
2)You can use the unbrick procedure in my signature below !

Bricked LG G3 [D855], cannot enter download mode

Hi, I was trying to flash a kdz to my LG G3 in order to downgrade the phone to 5.0. However, while the program start flashing and the progress bar on the phone reach 5%, the program shows " cannot reach the sever". The flashing process then stopped, no matter I keep clicking "retry".
As a result, I took out the battery and put it back attempt to get back to download mode.
However, the LG G3 do have a starting up screen as usual, but the phone didnt go in download mode, but get into black screen. The notification light is repetitively flashing blue and red color for couple second.
THe computer cannot detect the phone.
Any idea how I can save the phone ~_~?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana

Bananaphone64 said:
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Click to expand...
Click to collapse
It can go into the recovery mode but not the normal OS. But what I can do in the recovery

voot566 said:
But what I can do in the recovery
Click to expand...
Click to collapse
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana

Bananaphone64 said:
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Click to expand...
Click to collapse
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"

voot566 said:
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
Click to expand...
Click to collapse
drivers installed?

Bananaphone64 said:
drivers installed?
Click to expand...
Click to collapse
Yes, driver is installed :crying:
but windows doesnt seems to have detected my phone

Hm... i recently havent the stock recovery installed. I allways hat the possibility to use TWRP.

Thx so much, Bananaphone64.
I think what the real problem now is, the computer cannot recognize the phone. Anyone else have an idea?

In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana

Bananaphone64 said:
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Click to expand...
Click to collapse
I have attempted on another computer, but the other computer also doesnt recognize the phone.
What is a SS?

A Screenshot or Picture from the Recovery Menu

Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS

I have seen that screen! 3 days before!
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!

yosmz1112 said:
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
Click to expand...
Click to collapse
Yes. it was completely not able to enter into the download mode...........

Wh0CaREs said:
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
Click to expand...
Click to collapse
It is factory recovery. let me check the link, thx so much

deleted

Lineage on the Gigaset GX290 Plus - maybe the GS290 helps?

Hi there,
finally, after all this time living without, i was thinking about buying a smartphone. My first one. And i found a device that seems pretty nice, the Gigaset GX290 Plus (here is it's official website).
But i don't want to use "defalut-Android" and would love to install Lineage OS on it.
Sadly, that doesn't seem to be possible... or is it?
There are instructions for a very, very similar Gigaset phone - the GS290, for example here or there.
The GS290 is also available with the /e/ OS pre-installed (but i'd prefer Lineage OS).
And in the /e/ forum, this information from Gigaset states, that the GS290 and GX290 indeed are very similar. And as far as i can tell, the "Plus" version is just a minor update, but still having mostly the same hardware.
So... there are people out there having Lineage OS on the GS290. Thinking about the similarity to the GX290... could there be a chance to get Lineage running on this rugged phone?
Any ideas and thougts are welcome. Thank you!

Hello
I have had the same idea ..
As before i had installed /e/ on a samsung S9 + very easilywith the documentation and the software . Honestly i am not a real geek.
Before I had a Xcover with cynanogen mod and it took me some efforts to make it !
SO i had written to GS and /e/ about this matter .
GS : no communication and / Or knowledge of the situation ( but /e/ is selling already new GS 290 with /e/)
/e/: no answer yet .
I assume it could be possible , but not so easy .
BUT there is a big potential of buyers :
riders,hikers,building workers... needing a hard phone with long time battery and NO droid or gogol sttuff

Cheers, https://github.com/GS290-dev/android_device_gigaset_GX290-unified exists. Me or Erfan will probably create an proper thread here soon, with precompiled rom zips.

Hi @nift4, any update on this?
nift4 said:
Cheers, https://github.com/GS290-dev/android_device_gigaset_GX290-unified exists. Me or Erfan will probably create an proper thread here soon, with precompiled rom zips.
Click to expand...
Click to collapse

markdegroot said:
Hi @nift4, any update on this?
Click to expand...
Click to collapse
I'll create a fresh build and post it here in a few hours

https://dl.nift4.org/lineage/GX290/lineage-19.1-20220408-UNOFFICIAL-GX290.zip
Works fine in my testing, though I didn't try that build specifically. Please note that Android 12 is still kinda WIP, but report all issues you find.

Should I sideload this zip file?

whats-in-a-name said:
Should I sideload this zip file?
Click to expand...
Click to collapse
The concrete instructions are:
1. Unlock bootloader
2. Flash this recovery image: https://dl.nift4.org/lineage/GX290/recovery.img
3. Reboot to recovery
4. Sideload and factory reset

Bummer, it did not work. I have a gx290 (not plus)
E:failed to verify whole-file signature
E: error 21

whats-in-a-name said:
Bummer, it did not work. I have a gx290 (not plus)
E:failed to verify whole-file signature
E: error 21
Click to expand...
Click to collapse
Were there no other errors? Or a prompt asking you if you want to skip the verification?

Nice to see I'm not the only person with this phone. Overjoyed I unlocked my bootloader which, interestingly, didn't require fastboot oem unlock but instead fastboot flashing unlock and fastboot flashing unlock_critical. I then flashed the recovery - which seems to have worked - and sideload the version of the rom you provided. This has bricked my phone, as it won't progress past the bootloader and the unlocked bootloader warning.
I was - of course - fully aware of the risks, and realize it's probably my own fault, but I still don't really know what's wrong.

ewy0 said:
Nice to see I'm not the only person with this phone. Overjoyed I unlocked my bootloader which, interestingly, didn't require fastboot oem unlock but instead fastboot flashing unlock and fastboot flashing unlock_critical. I then flashed the recovery - which seems to have worked - and sideload the version of the rom you provided. This has bricked my phone, as it won't progress past the bootloader and the unlocked bootloader warning.
I was - of course - fully aware of the risks, and realize it's probably my own fault, but I still don't really know what's wrong.
Click to expand...
Click to collapse
If you get to the unlocked bootloader warning, can you get through to the recovery and format data? That might be enough to fix the soft brick

ewy0 said:
Nice to see I'm not the only person with this phone. Overjoyed I unlocked my bootloader which, interestingly, didn't require fastboot oem unlock but instead fastboot flashing unlock and fastboot flashing unlock_critical. I then flashed the recovery - which seems to have worked - and sideload the version of the rom you provided. This has bricked my phone, as it won't progress past the bootloader and the unlocked bootloader warning.
I was - of course - fully aware of the risks, and realize it's probably my own fault, but I still don't really know what's wrong.
Click to expand...
Click to collapse
GX290_android9_2019-07-31.zip | by gajus for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
you can go back to stock android 9 with flashtool (windows)
I did this five times at least, experimenting with the different buillds.

whats-in-a-name said:
GX290_android9_2019-07-31.zip | by gajus for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
you can go back to stock android 9 with flashtool (windows)
I did this five times at least, experimenting with the different buillds.
Click to expand...
Click to collapse
A precondition to installing is having Android 10 installed so don't forget to update afterwards

I loaded three updates, now on Android 10
1. fastboot flash recovery recovery.img
2. power down.
3. volume UP and power, release power button.
4. in custom recovery, factory reset + clear cache
5. sideload lineage
6. reboot to system
phone hangs at bootlogo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

whats-in-a-name said:
I loaded three updates, now on Android 10
1. fastboot flash recovery recovery.img
2. power down.
3. volume UP and power, release power button.
4. in custom recovery, factory reset + clear cache
5. sideload lineage
6. reboot to system
phone hangs at bootlogo.
View attachment 5605575
Click to expand...
Click to collapse
Edit: Does it hang or reboot?

Apparently both you have that issue which is strange as it works for me, I'll try to replicate what you guys did and report back, thanks for the feedback

nift4 said:
Edit: Does it hang or reboot?
Click to expand...
Click to collapse
It hangs at: orange state
this device cannot be trusted
wait for 5 seconds to boot (which takes forever)

I'm back to stock Android 10, installed custom-recovery and boot into recovery, all well. But after that, when I boot into system once... I cannot boot into custom recovery, I get the stock recovery back. So it is not persistent.

whats-in-a-name said:
I'm back to stock Android 10, installed custom-recovery and boot into recovery, all well. But after that, when I boot into system once... I cannot boot into custom recovery, I get the stock recovery back. So it is not persistent.
Click to expand...
Click to collapse
That is wrong, it is persistent. It's just that system is overwriting recovery to make your life more annoying

Found my old note 10.1 and did something stupid... need help...

I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Why don't you try flashing stock firmware?
Check for drivers issue.

mvikrant97 said:
Why don't you try flashing stock firmware?
Check for drivers issue.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
Your device should show up like this in device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing like this

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
It is P605. And from this post looks like you are not the only one https://forum.xda-developers.com/t/q-galaxy-note-10-1-2014-not-recognized-in-download-mode.2494886/

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Also watch this video

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Please try to get into download mode for odin to recognize your tablet

Ok, so using another PC and yet another cable, I was finally able to see this pop up on the device manager when in the "update with adb" option:
Unfortunately, I cannot get the tablet to stay in download mode. As soon as I confirm to go to download with the vol+ button, it immediately starts to boot loop.
On the other hand, when in the adb mode, the PC does recognize the device when it's attached and I can see it with "adb devices" command.
But unless there's a way to get it to go to download mode, I'm screwed, right?

mvikrant97 said:
Also watch this video
Click to expand...
Click to collapse
Yes, but that is my problem. I cannot get to the download screen. I can press up to select it, but then poof, it goes to cycle again. Unlike the guy in the video:

OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!

erkme73 said:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
Click to expand...
Click to collapse
Now you are good to go. Odin will detect and you can flash it.

Thanks... doing it now. I'll let you know how great you are as soon as it starts working! Thanks...

Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
That's great to see your device is working now.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
If you really wanna stay on stock you can use Chainfires Autoroot for this device.
Anyway, my P605 is on LOS17.1 running stable.