Related
CURRENT UPDATE 25/6 :
unlocked the bootloader and flashed the O.S (5.0.2) without erasing userdata.
stock recovery mode works now.
booted using custom recoveries : a)TWRP 2.8.X.X b)Philz Touch (will add details later)
data recovery almost done.
NEXT STEP : time to install a CLEAN STOCK ROM
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is LOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Media Manager (when connected through USB)
{
"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"
}
What Happened :
Day before : Phone switched off at 0% battery.
Put for recharge the next day (29/5) and I tried to switch it on as it reached 35%.
Didn’t boot.Tried a few more times.
I can access :
Only the bootloader
Problem after Moto Boot Animation
http://imgur.com/l5bUHyq
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3l72ArFhLc1ZThqU3ZoY29hWWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3l72ArFhLc1LWJ2VXI3SmxEQjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B...k50a3VEa1RmZGkwRjJja3E5M0NpSHQzQ3c&authuser=0
Windows Device Mgr:
http://i.imgur.com/lGjFzDR.jpg
What I tried :
http://i.imgur.com/Lq9qHs1.jpg
(suggested on motorola website)Reboot - 10 seconds
(suggested on motorola website)Reboot - 120 seconds power button
Erased cache using fastboot - works.
Recovery mode : I got “bootup failed”
ADB not able to detect the device.Fastboot can.
PC able to detect USB but as a “Falcon Device”
WHAT I WANT :
I want to get a copy of all my internal SD Card data,eg : photos,Contacts,WhatsApp folder,etc.
Flashing it in any way that causes data loss would be my last option.
Besides,i don't have relevant experience and would be asking a friend who has experience with this stuff.
What I found out :
Bootloader UNLOCK will wipe all my internal memory user data.
To root the phone,I’ll have to UNLOCK the Bootloader.
ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
Battery drained to 0% from 75% in one night when i kept the phone in the blank but bright screen mode.
STEPS AHEAD :
Service Centre Visit (Saturday) - Problem Detection -> Won’t be giving the phone since they might damage the data in a situation where it can be recovered.
More Research about such cases and solutions?
Eg : Battery replacement,re-adjustment.
Any way to make it appear as a storage volume on PC?
Any links,suggestions,etc. can
Motorola Support Says :
Service Centre can help
ADB Reqd to recover data
Or use backup software (how can I do this when i am not able to boot :| )
Went to a Service Centre today,they said they will have to "download" software to the phone to check for problems
So my data will be lost.
So I am currently searching for more solutions.
ANY ADVICE,TIP,COMMENT or even a positive post would be really appreciated.THANKS FOR READING
Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup
Thanks for reading and giving your suggestion
I've never rooted,flashed or unlocked my device,no major modifications as well.
So no custom recovery.
I tried what you suggested but it didn't work for now.
Here's what I got :
Maybe because of the LOCKED Bootloader.
ADB doesn't detect my device probably because i don't have debugging enabled.
Thanks Again @lost101
lost101 said:
Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup
Click to expand...
Click to collapse
@ravibhat - Could you unlock the Bootloader? See FAQ for instructions: http://forum.xda-developers.com/showthread.php?t=2537119
@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want
ravibhat said:
@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want
Click to expand...
Click to collapse
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
Doing only the above commands will not erase userdata, only reinstall Android.
Hey @lost101,
I'll be using the firmware for XT1033 (Asia-Retail 5.0.2) since the one i have is the dual-sim version.
I came across additional commands in this format:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo Moto-logo.bin
fastboot flash boot boot.img
<SYSTEM IMAGE FLASH FILES go here - 4 commands like you said here since it's Lollipop>
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Since I want to save my data i won't be using "oem unlock" and "erase userdata" commands.
So,
a) Can you tell me if there's a specific reason you didn't add them?Will they damage or reset any of my data or affect user partition?
They were also mentioned by a few folks who are trying something similar while trying to protect their data.
I thought they were part of the process.
b) mfastboot or fastboot - will using the normal "fastboot".exe cause any problems?And so you suggest mfastboot?
And thanks a lot for helping me out
lost101 said:
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
Doing only the above commands will not erase userdata, only reinstall Android.
Click to expand...
Click to collapse
@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.
Hey @lost101!
Man,i tried the commands you mentioned first,didn't work.
Also tried it with the other commands,still no result.
Overall : i didn't get any errors except the ones where i tried to flash a custom recovery.
When i choose the "Recovery" option in the bootloader - I get "booting failed" error for both stock and custom recovery images.
Also,i couldn't directly boot using a custom recovery image file using the "boot" command.
Is it something to do with the files i used or...something else?
Any other tips?
lost101 said:
@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.
Click to expand...
Click to collapse
@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
@deej_roamer @deeplyyoung : thoughts and advise please
ravibhat said:
@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
Click to expand...
Click to collapse
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.
Hey @lost101
Sorry for not being clear.
Here's the exact response :
Response on the screen:
The responses upto "boot up failed" in the below image were the ones i got while trying to flash recovery images.
The responses below it are the ones i got for flashing those 4 commands.
After this when I try to bootup - the same problem as mentioned in the main thread - getting stuck after Motorola Logo on a blank but active screen.
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3...WWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3...QjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B3...Q3c&authuser=0
Anything else you'd like to know that can help
lost101 said:
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.
Click to expand...
Click to collapse
@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)Has anything changed if you let Android boot?
@lost101 :
ADB can be used but when i searched,USB Debugging Enabled seemed to be a per-requisite in almost all cases on XDA and other forums which I can't do right now since no access to settings.
Push,Pull can be used to backup and restore - tried this on an emulator (Bluestacks on PC) which was detected by it (image below).
My driver is :
I'm not sure if it's the right one or not,no way to test it except testing with "adb devices" in command line but fastboot works so i guess it is.
Fastboot works well in the bootloader,it was able to flash all system images including the ROM.
I am not sure whether this device is hard-bricked since i haven't tried the "fastboot erase userdata command".
No change in the Android boot up process - it's the same issue as before.
It took a little more time (5-10 seconds more to arrive at the blank but lit screen as in the video mentioning the problem) after those 4 commands but that was most likely due to stocking the new firmware.
What bothers me is that i am unable to boot into recovery directly or boot into it after flashing.
It shows "boot up failed" even for the flashed recovery.
lost101 said:
@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)Has anything changed if you let Android boot?
Click to expand...
Click to collapse
There is another command: adb reboot recovery
I am no longer clear. Can you access stock recovery mode? Power on while holding Vol up?
@lost101 :
adb doesn't work as i mentioned since it doesnt detect the device,probably since ADB debugging wasn't enabled.
And i cannot access stock recovery (like previously mentioned in the OP - same issue ) - it gives "boot up failed" error on the device.
These are the commands i can use right now (since only fastboot works) :
I would really like to save the data but if that's really not possible or practical at this point,i'd go for the second best option.
Unlock the bootloader - try flashing custom/stock images or recovery - take backup or use recovery software.
Any suggestions on unlocking the bootloader?
@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'
@ravibhat
OK so i have understood what problem you got
Now since you wanna save you data here's what you need to do( if it actually works)
As the system boots up, after 2 or 3( not exact) seconds the data partition is mounted ( this is necessary to boot up OS )
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report
@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.
Hey @lost101,
I am able to boot into the bootloader and use fastboot commands.
But when i select "Recovery" on the bootloader as shown in the image in the above post,it says "boot up failed".
I've flashed stock recovery and it was successful but unable to boot directly using "flash boot recovery.img" or even after successful flashing (by choosing Vol down button to navigate and then Vol Up button to select while in the bootloader)
lost101 said:
@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'
Click to expand...
Click to collapse
@sjandroiddeveloper
ADB doesn't detect my device.Is USB Debugging required to be enabled to use ADB ?
I don't have USB debugging enabled (it was disabled by default).
sjandroiddeveloper said:
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report
Click to expand...
Click to collapse
Yes,i saw a lot of posts suggesting this but unfortunately the device doesn't get detected by ADB,also i don't understand the reason why i can boot into Stock Recovery despite being able to successfully flash it,it always says "booting failed".
lost101 said:
@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.
Click to expand...
Click to collapse
Hi, my son's oneplus one mobile will not start up. When we press the "on" button, we see the first "1+ powered by android" screen, then the word "cyanogen" is written across the screen. This word continues to slowly blur and un-blur slightly, but the system never comes any further. (The phone is fully charged).
We can also boot to a "cyanogen recovery" screen, where there are several options - where I guess a "factory reset" could be worth a try. If we do a factory reset, is there any way to maintain installed apps, and especially "progress" in these apps?
Thanks for any help,
Peter
You could try to use adb to backup the data, but you wont be able to save the progress in the apps I think, some apps have their progress stored online with your google account(Clash of clans for example)
ok, thanks (I don't know what "adb" is, but I'll google it).
Otherwise, has anyone seen this startup problem before, and are there any good solutions?
Thanks.
Hmm, seems that "adb" requires installation and/or enabling on the phone - as I can't start the phone, I don't think I can use this unfortunately.
You don't have access to adb unless it was previously enabled. Can you shed some light on what caused this situation please? It makes it a lot easier to troubleshoot. Do you know what build of Cyanogen OS was installed on the phone before this happened?
Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.
xdzgor said:
Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.
Click to expand...
Click to collapse
Ok, thanks. If you can get into the stock recovery you should try flashing the latest build from here, then reboot the phone.
Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options:
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
Can we use one of these to upload a new OS to the phone?
"Apply update" gives the options:
apply from ADB (does this mean adb *is* running on the phone?)
choose from internal storage
"Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.
xdzgor said:
Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options:
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
Can we use one of these to upload a new OS to the phone?
"Apply update" gives the options:
apply from ADB (does this mean adb *is* running on the phone?)
choose from internal storage
"Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.
Click to expand...
Click to collapse
That's the stock recovery. The "apply from adb' option is present whether you have adb enabled or not, so that's a no-go. I've just realised that you won't be able to use the recovery to flash the zip anyway, because there's no way to transfer the zip to the device without adb.. I think your only option will be to unlock the bootloader and flash the stock images with fastboot. Unfortunately this will erase all data on the phone, but right now you don't really have any other option. So what you'll need to do is this:
1. Install adb/fastboot onto your PC, the 15 seconds adb installer is probably the easiest option for this.
2. Use the reboot to bootloader option in recovery to put the phone in fastboot mode.
3. Navigate to where adb.exe and fastboot.exe are located on your PC, hold shift and right-click, then select open command prompt here.
4. Make sure your phone is connected to the PC via usb cable and (in the terminal window that popped up after the previous step) issue this command:
Code:
fastboot devices
It should return the serial number of the device, if it does you have a working fastboot connection. If it doesn't return the serial number you might have to play around with drivers.
5. Once you know you've confirmed that you have a working fastboot connection you can check the status of the bootloader with this command:
Code:
fastboot oem device-info
There will be a few lines of text. One of the lines will be 'bootloader unlocked: true/false". If it says true you can move on to step 6, if it says false you will need to unlock it with step 5a.
5a. Unlock the bootloader with this command:
Code:
fastboot oem unlock
The phone will automatically go through the unlock process, and will probably try to boot into the OS. Get back into fastboot mode by using the option in recovery, or by shutting the device off by holding the power button and then using the fastboot mode button combo (hold power + volume up).
6. Once you know you have an unlocked bootloader you can now flash the stock images to the device:
-Download the latest stock images to your PC from here. If you don't want the latest build you can find all stock images mirrored here thanks to @Spannaa.
-Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
-Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
-Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot flash dbi sdi.mbn
Code:
fastboot flash aboot emmc_appsboot.mbn
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot flash tz tz.mbn
Code:
fastboot flash LOGO logo.bin
Code:
fastboot flash oppostanvbk static_nvbk.bin
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
Please note: flashing the userdata will wipe your internal storage (your virtual sd card). It's possible to flash these images without that command if a full wipe isn't completely necessary in your situation.
-Reboot your device with this command:
Code:
fastboot reboot
-It's now safe to disconnect your usb cable.
Click to expand...
Click to collapse
Hopefully the phone will boot up now.
Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)
xdzgor said:
Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)
Click to expand...
Click to collapse
The best way is by creating a backup with TWRP recovery. You'll find instructions on how to flash it (and how to make a backup) in my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Hello i'm a french guy
**
I just recovered TF300T stuck on trwp 2.5.0.0 at startup.
At each start I have the ASUS logo with top unlock.
then teamwin logo
Then TWRP 2.5.0. starts
*
I think a wipe was done on this tablet erasing all data has therefore brig.
*
I followed the tutorial from xda
*
* http: //forum.xda-dev...13&postcount=12
*
http: //forum.xda-dev...d.php t = 2528976
*
but I was unable to find the right driver for Windows recognizes the tablet device driver because in it but I Appear not manage to install the drivers.
*
I did the manipulation on a 2 pc in seven different 64-bit in the other 32bits nothing products.
*
The tablet is definitively dead or there's there a solution
*
Thank you in advance for your help.
nico2048 said:
Hello i'm a french guy
**
I just recovered TF300T stuck on trwp 2.5.0.0 at startup.
At each start I have the ASUS logo with top unlock.
then teamwin logo
Then TWRP 2.5.0. starts
*
I think a wipe was done on this tablet erasing all data has therefore brig.
*
I followed the tutorial from xda
*
* http: //forum.xda-dev...13&postcount=12
*
http: //forum.xda-dev...d.php t = 2528976
*
but I was unable to find the right driver for Windows recognizes the tablet device driver because in it but I Appear not manage to install the drivers.
*
I did the manipulation on a 2 pc in seven different 64-bit in the other 32bits nothing products.
*
The tablet is definitively dead or there's there a solution
*
Thank you in advance for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Maybe read my thread here ....
Thx Josh
Thank you
I had not seen that the post but my problem is that I have come to update the drivers for the peripheral road manager the tf30t. I have an exclamation point in front.
Hello
after quite a hack I managed to run the command adb reboot bootloader and I have 3 icons.
By clicking on the android tablet reboot by restarting but I find myself again TWRP. What you have to manipulation and after how to update and install TWRP lolipop.
Thank you for the help and the forum but for a french is not so simple as that
nico2048 said:
Hello
after quite a hack I managed to run the command adb reboot bootloader and I have 3 icons.
By clicking on the android tablet reboot by restarting but I find myself again TWRP. What you have to manipulation and after how to update and install TWRP lolipop.
Thank you for the help and the forum but for a french is not so simple as that
Click to expand...
Click to collapse
You need to follow my guide ?
It is that simple .....
Thx Josh
Get back to bootloader (3 icons) and then try this command on your computer:
fastboot devices
if it will detect anything then you can try erease procedure by @Buster99 :
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
then after clean memory flash fresh official JB downloaded from asus website (unzip file untill you will have file called "blob")
fastboot -i 0x0b05 flash system path_to_blob
example:
fastboot -i 0x0b05 flash system c:\android\blob
this would take like 5 minutes, then:
fastboot -i 0x0b05 reboot
and you should be back on stock
I had slightly different issue - TWRP flash failed and I had only android booting - even after manually flashing recovery again via fastboot
this clean swipe got me going again - upgraded to 5.1.1 and set it up again
Sent from my TF300T using XDA Free mobile app
th3cr0w said:
Get back to bootloader (3 icons) and then try this command on your computer:
fastboot devices
if it will detect anything then you can try erease procedure by @Buster99 :
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
then after clean memory flash fresh official JB downloaded from asus website (unzip file untill you will have file called "blob")
fastboot -i 0x0b05 flash system
example:
fastboot -i 0x0b05 flash system c:\android\blob
this would take like 5 minutes, then:
fastboot -i 0x0b05 reboot
and you should be back on stock
I had slightly different issue - TWRP flash failed and I had only android booting - even after manually flashing recovery again via fastboot
this clean swipe got me going again - upgraded to 5.1.1 and set it up again
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Yep, that is what my guide is, thx for the double post
Hello
it works thank you for your help
Now how to install TWRP and lolipop
Hello
thank you for the help I have finally managed to install lolipop zombie pop thanks to the tutorial and help.
It just remains for me a problem when I plug the dock touchpad does not. I was thinking activate it with the button but nothing happens.
lj50036 said:
Yep, that is what my guide is, thx for the double post
Click to expand...
Click to collapse
Heh heh heh, sad but true. Made me laugh!
Hello everyone,
this is about the Nexus 5 16gb.
It has been completely erased and no backup has been done by the previous owner :silly: and he asked for help. I am a complete noob myself and could only do the below listed things thanks to this forum.
It was completely empty when I received it (as far as I can tell), but I can access the bootloader. I put a costum recovery on it with the help of this forum. When in costum recovery mode my computer identifies it as the Nexus 5 with the help of the Google Drivers and the SDK-Android (I presume) I installed previously.
I went to Google and was able to put a factory image on it from their collection of "hammerhead" for Nexus 5 (GSM/LTE).
I tried the 6.0.1 (MOB31E) and installed it via the flash-all.bat via CMD since this version was, according to the owner, installed before. It worked, as far as I could tell - data got copied on the phone.
When I restart the phone, the Google Logo with an opened lock blinks very slowly. The swirly loading screen I have seen on some Youtube videos for this model's OS does not appear. I presume that the phone does not recognize the flashed factory image?
My question is:
Do I need to try all of the factory images from Google until one works? Or is something so fundamentally lost (maybe somewhere in the booting process), that the phone cannot be repaired since the swirly loading screen does not appear?
Do I need to copy something else on the phone besides the factory image for it to start the booting process for the OS that I have installed via the flash-all.bat?
I am very lost - if someone could point me toward the right direction or even just toward the right kind of tutorial, I'd be very grateful.
You can flash the factory image using the following fastboot commands (subtitute file names to match the file names from the unzipped factory image):
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
I've got a BIG problem with my new Pixel 5. I've successfully rooted it and had it operating for a day.
I then decided to boot into recovery mode just to see what the new stock recovery looks like (I used to use TWRP.).
BIG MISTAKE!
All I got was the error icon that I've seen in the past meaning that no recovery image is available. OK, so I try to just try to do a simple reboot. I'm taken back to the same place.
Now I try to reload Android. No luck! I'm stuck on:
"Device product is 'unknown'"
Update requires 'bramble'.
HELP!!!!
In the file android-info.txt, what would happen if I patched the line
require board=bramble
to
require board=unknown
Did you figure this out? I'm facing the same issue with my Pixel 5.
Edit: I figured it out. If you are having an issue with the 'flash-all.bat' command like we were, you just need to manually push the individual files and it should boot you back up into stock.
Run these commands:
1. fastboot flash bootloader <bootloader image file>
2. fastboot reboot-bootloader
3. fastboot flash radio <radio image file>.img
4. fastboot reboot-bootloader
5. fastboot update <image zip file>.zip
6. fastboot reboot
All of the reboot-bootloader commands may be redundant but it worked for me. It booted me into stock, verified I was unrooted with Root Checker, then proceeded to reboot back into the bootloader and 'fastboot flashing lock' to re-lock my bootloader and wipe the device.