Related
I updated TWRP today to 2.3.0.0 from within GooManager then rebooted into recovery and fixed my permission. It was done unusually fast and when I rebooted, it would get stuck on the booting screen. When I tried to boot into recovery by pressing power and both volume buttons, it would get stuck on the google logo.
Please advise.
Any other way I can fix this or somehow restore from a backup?
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you very much!
I'm sorry but I'm not too much of an expert on Android. AFAIK Recovery mode is the only way I know to do some low system stuff. If I can't boot into recovery, how else can I do anything to fix this?
How can I revert back to old version?
I know you linked the other thread but there are 33 pages I was hoping you would have a short answer hehe thanks.
Is it constantly rebooting at the google screen or just stuck?
goofball2k said:
Is it constantly rebooting at the google screen or just stuck?
Click to expand...
Click to collapse
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
I see that you posted over on the twrp thread, hopefully those guys can help you. I am assuming that you have updated to 4.1.2? If you're really stuck maybe try a tool kit like wugs or n7 toolkit? Sorry but SDK isn't one of my strong points either
Sent from my Nexus 7 using xda premium
woshiweili said:
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
comminus said:
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
woshiweili said:
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
Click to expand...
Click to collapse
Hey, glad to hear you're in. In an earlier post you described
woshiweili said:
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
which sounds like you were able to get to fastboot mode (power + vol buttons) - your N7 should look like this. From there you can issue fastboot commands to the device to flash recovery. kerne, and bootloader to name a few.
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
woshiweili said:
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
Click to expand...
Click to collapse
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
comminus said:
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
Click to expand...
Click to collapse
Thanks for all your help comminus!
Fortunately I was able to wipe everything while I was in recovery and restore from my most recent backup and now it's working fine. At the very least it's allowing me to boot into system
OK I'm really not rebooting for a while lol
I installed twrp a few weeks ago through GooManager and made a backup. When the 4.1.2 update came out, I downloaded it manually with the intent on flashing it via cu custom recovery, but low and behold twrp wasn't working at all. Even with my device plugged into my Win 7 pc... nothing but the exclamation point droid.
I was able to install an updated version of twrp and get everything sorted out, but now I don't have a lot of faith in it, and am booting into recovery at least once a day to make sure it's still working. I never had any problems with cwm.
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
I'm using twrp version 2.3.0.0, and have no plans on updating it because it's stable and working great now
Gigabitex2 said:
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Updated to 2.3.1.0 but still having booting issues
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
ZyreHD said:
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
Click to expand...
Click to collapse
setup adb and learn how to flash back to stock in fastboot. you will never brick your device beyond repair as long as you are capable of following directions for flashing and rooting and such
Here's the sticky from the other forum.
That is very useful and they talk in layman's terms. When I first got my N4, I followed this and got custom everything following the instruction posted there.
I'm no expert, but I rooted my N4 in the first week very easily, and as long as you follow all the instructions in the XDA thread then you won't go wrong. If you are really worried then you can use a toolkit as that will automate everything, but I'd never recommend that as you aren't really learning.
As for backing everything up, you can back up some things like your contacts, WiFi passwords and so on to your Google account. Apps is a lot harder if you want the data, but I believe an ABD backup will work - again, look at the appropriate thread (or use the toolkit for backing up).
And Roms, most of them have a stock feel with more features such as extra customization, but if you want a different look you can use themes - you can get touchwiz themes on the play store for ROMs like CM.
Sent from my Nexus 4 using xda premium
you dont need root to flash roms or kernels, you need a custom recovery(and an unlocked bootloader). you need root to run root apps and to mess around with the root file system.
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
username8611 said:
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
Click to expand...
Click to collapse
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
ZyreHD said:
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=2010312 well, it will show you exactly how to get back to stock if need be.
We were all scared and nervous too when we first rooted an android device. Lol. When you get it done you soon realize how easy it was. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Can someone help? So I have Cyanogenmod installed on the phone and got USB debug on. When i unplug and go into the bootloader and then plug the micro-usb in my PC doesn't detect the phone. I do have the drivers installed.
It did work, now it doesn't meaning I can't perform the stuff needed.
ps: If your wondering if I use the SDK to put everything to stock well sorry but I can't get the SDK to work. Java issues and errors. Pain in the ass so I stop with that.
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Edit 2: 5min later and still at the X logo. It does move but nothing. Is my phone dead?
ZyreHD said:
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Click to expand...
Click to collapse
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
im not sure if i reading it right, but from what i can gather, you flashed cm10.1, then found out adb doesnt work right so you are ditching it and going back to stock? i wouldnt worry about it too much. as long as you can still use fastboot in the bootloader, thats all you need to do anything to save yourself from certain death. adb is more helpful for gathering up data if you cant lose it before flashing back to stock
username8611 said:
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
Click to expand...
Click to collapse
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Edit 3:
Retrying in the meantime. Now at writing system (done)
Edit 4:
Now I'm at the point where it's erasing userdata....
Edit 5: couple of minutes later and still going.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Click to expand...
Click to collapse
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to the bootloader. type this in fastboot, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
username8611 said:
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to fastboot. type this, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
Click to expand...
Click to collapse
I got a different option now. format userdata and I get options. Flash all, erase, update filename etc.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Click to expand...
Click to collapse
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I only have 4 options there.
Reboot system now
apply update from ADB
wipe data/factory reset....
Oh I got it. It formatted and I rebooted. For now it only shows the X logo. Will go downstairs in the meantime to get something to drink. It might take some time maybe?
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
nevermind, you were talking about the options in recovery
ZyreHD said:
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
Click to expand...
Click to collapse
Congrats. That's why I wrote what I did in your other thread. Read, read, read. Its better to know how to fix things before they happen then frantically trying to find out how fix them while they happen.
Sent from my Nexus 7 using xda premium
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
GuyWithBrokenPhone said:
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
Click to expand...
Click to collapse
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
GuyWithBrokenPhone said:
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
Click to expand...
Click to collapse
It definitely shouldn't have taken that long. Can you boot into the recovery?
Sent from my Nexus 7 (2013)
Just put your phone in fastboot mode and flash factory image.
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
That's normal for stock recovery, you won't be able to sort your phone from there, stay in fastboot mode. You can use a toolkit to flash back to stock from there if you need it more noob friendly. Otherwise you can use the flash-all.bat script in the factory images.
GuyWithBrokenPhone said:
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
Click to expand...
Click to collapse
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
audit13 said:
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
Click to expand...
Click to collapse
Oh god thank you.
Okay. I'm trying to reinstall Paranoid Android now. I did the sideboot via ADB.
I couldn't seem to get the stock version of android on it though. I made sure to open the tar file and tried to move the .zip "image-occam-jdq39.zip" onto the phone, but it wouldn't accept it. So I'm trying Paranoid android again.
Edit: I got it booted. But now wifi won't work. Neither the speakers.
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
DrFredPhD said:
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
Click to expand...
Click to collapse
Doing so now. If I had known about this tool before, I probably would have been done with this a lot sooner.
Currently flashing stock and unrooting.
The toolkit is most certainly the way to go. No mess, perfect every time for me.
Sent from my Nexus 4 using Tapatalk
Hello,
I've got a problem. On monday my Nexus 7 2012 (with lastest stock Android) froze and I had to reboot it. But then it got in a bootloop where it would boot to the boot-animation (the four moving dots) and then restart after half a minute. Then I went into the bootloader to switch it off. When I switched in back on it just got stuck at the google logo.
I tried to reflash the stock rom, but I haven't unlocked the bootloader yet and everytime I try to do unlock it, it fails with "unknown error code".
At first I used Wug's Toolkit. When that didn't work I used cmd, but that doesn't work either.
I would really appreciate some ideas to solve that
You dont have to unlock the bootloader to flash factory images.
You can flash it with fastboot or a toolkit.
Did you try to get into recovery?
Maybe you can wipe some thing like cache, dalvik cache and system,
And then install the firmware again.
I once installed a firmware without properly wiping and also got stuck in thjis animation logo.
After wiping in recovery and re-flashing the firmware it worked again.
Erovia said:
You dont have to unlock the bootloader to flash factory images.
You can flash it with fastboot or a toolkit.
Click to expand...
Click to collapse
As far as I know, you need to unlock the bootloader. Anyway, I tried a toolkit as well as fastboot via cmd but none worked.
See here: http://forum.xda-developers.com/showthread.php?t=1907796
In order to do anything useful in fastboot, the bootloader must be unlocked
Click to expand...
Click to collapse
Amlan90 said:
Did you try to get into recovery?
Maybe you can wipe some thing like cache, dalvik cache and system,
And then install the firmware again.
I once installed a firmware without properly wiping and also got stuck in thjis animation logo.
After wiping in recovery and re-flashing the firmware it worked again.
Click to expand...
Click to collapse
I dont't have any custom recovery installed. When I am trying to access the stock recovery mode via the bootloader then I get to the Google logo and "booting failed" is written in the upper left corner.
My guess is that the emmc is broken
Google search android factory images, download the appropriate one for your device
Then extract contents and double click the flashall.bat
If this fails then chances are your emmc has been severely corrupted, I've seen a few get to that point with the booting failed and its 50/50 if they resurrect their device
Best of luck
(Oh and don't use toolkits)
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Google search android factory images, download the appropriate one for your device
Then extract contents and double click the flashall.bat
If this fails then chances are your emmc has been severely corrupted, I've seen a few get to that point with the booting failed and its 50/50 if they resurrect their device
Best of luck
(Oh and don't use toolkits)
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that again the way you described it and sadly it didn't work. I have to accept that the emmc is corupted.
Thanks guys for your help anyway
Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?