Database Users

Nexus 7 wont boot pass google logo after root/unroot

I got a nexus7 a week ago but decided to root the device today just to try apps which require root, i rooted it fine but i decided to unroot and thats where the problem started i cant boot pass the google image, i can get into where you hold down volume and power for so many seconds and team win recovery which says i have no OS in the reboot section, i've tryed nexus 7 toolkit v3.2.0 and nexus root toolkit to restore back to factory system but no luck, so is it me doing something wrong or is my nexus 7 just a paper weight now.

Doubt it,
Being you still have a custom recovery you didn't follow the right steps to unroot, might need to unlock the bootloader again, but follow one of the many guides, and try to stay away from a tool kit
Sent from my HTC Vision using xda premium

Unlock bootloader
Flash boot, recovery, system, userdata.
Files are zipped in the factory images directly from google.
Wipe cache.
Relock bootloader.
Reboot into recovery.
Factory reset. (Nexus 7 will only see 8GB if you don't do this step)
That is the gist of how it's done.

I followed a step by step guide on laptop man website but when i come to flash the android image it says file too large, i used 4.2.1 from googles site, if i'm correct when you type fastboot -w update image-nakasi-jro03d.zip (in the walkthrough) i can replace it with a later newer android in this case 4.2.1 jop40d

You could do it that way. Some people have. Although I received an error every time I did.
I didn't receive an error when I flashed the files in the zip.
First make sure you have the correct factory image for your device downloaded.
Then make sure you extract the boot.img, recovery.img, system.img, and userdata.img files to your fastboot folder and perform the following actions...
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
Lastly, boot your system up into recovery and perform a factory reset from there. If you don't do the last step they you will be stuck with ouly 8GB, vice 16 or 32.
It's that easy.

When i try to boot into recovery mode i get the android mascot with a red triangle, does that mean i have no recovery file.
OOOPS the system booted up into android as the recovery mode didnt work (as above) is there anyway i can reset to factory settings to get the 32GB back as it shows 6GB.
Update: I think i sorted it out now somehow as it shows up as 27.oddGB now (about same as i got it) instead of 6GB, anyway thanks for your help, it seemed complex well it is but once you know whats what it's not so, the hardest part is getting the files and putting them in the right places

When I try to reboot to recovery via the bootloader it just hangs... Can boot to recovery inside android (usually using Rom Manager or another reboot application)... any idea why?

I have read reports that it will hang when booting into recovery if not connected to a PC.
And as for that triangle you see.... That's normal.
That means that your in recovery mode. Your menu is just hidden.
Press power and volume up to view it.

No fastboot, adb and bootlooping

Hi,
I have multirom installed and tried to install a android 5.0 rom. After installation I had some kind of boot loop: google logo -> restart
After that I rebooted via fastboot to recovery, but after the splash screen it rebootet and I got again the boot loop.
My next step was to try fastboot boot with the multirom recovery image and my default boot.img, but no success...
Then I noticed that I need for this 5.0 rom the 4.23 bootloader, so I upgraded from 4.13 (I think).
Same after that...
Then I tired fastboot boot with a stock TWRP recovery image for nexus 7 (2012) and I got a new kind of bootloop after that: google logo -> TWRP Logo -> restart
And now it tries to boot TWRP every time I turn on the devices and can't boot to fastboot (via vol - button) and adb is not working too...
Any ideas?

Download factory image and do a clean flash with wug tool kit. This will fix it.

To install the factory image, I need fastboot and I can't enter fastboot mode.

ThauExodus said:
Hi,
I have multirom installed and tried to install a android 5.0 rom. After installation I had some kind of boot loop: google logo -> restart
After that I rebooted via fastboot to recovery, but after the splash screen it rebootet and I got again the boot loop.
My next step was to try fastboot boot with the multirom recovery image and my default boot.img, but no success...
Then I noticed that I need for this 5.0 rom the 4.23 bootloader, so I upgraded from 4.13 (I think).
Same after that...
Then I tired fastboot boot with a stock TWRP recovery image for nexus 7 (2012) and I got a new kind of bootloop after that: google logo -> TWRP Logo -> restart
And now it tries to boot TWRP every time I turn on the devices and can't boot to fastboot (via vol - button) and adb is not working too...
Any ideas?
Click to expand...
Click to collapse
I was stuck the same way yesterday. Use the WUGS Nexus Root Toolkit. http://forum.xda-developers.com/showthread.php?t=1766475
I had to fool around with it before it would see the device, but once it did, I flashed the LRX21P and was off and running.

When I want to use in the toolkit "Back to Stock (Soft-Bricked/Bootloop) it asks me to tsrat into fastboot mode... but I can't... but I can get the device into apx mode...

Bump...

ThauExodus said:
When I want to use in the toolkit "Back to Stock (Soft-Bricked/Bootloop) it asks me to tsrat into fastboot mode... but I can't... but I can get the device into apx mode...
Click to expand...
Click to collapse
You mention TWRP - are you able to boot into TWRP, or does it just show the splash and reboot again? If you can get into TWRP, you could conceivably use ADB mode and sideload something...

Splash and reboot... I already tried to get adb access, but no success...

Nexus 10 (Manta) Stuck in Download mode after Unlocking

Hello XDA forums members. I need some help on recovering my Softbricked Nexus 10.
Here the situation. I unlocked the bootloader using Wug nexus toolkit. (Latest version as of typing is v2.1.9)
The procedure runs smoothly until the time to temporary boot to stock bootloader (Which does nothing btw)
I was thinking, what the heck, the unlock is already done, why not try booting to the stock recovery by Holding down Power+Volume Up
This was the time I realize my mistake, oh god. No Stock Recovery. Tried rebooting back to Fastboot. No Fastboot (When starting fastboot mode the tablet just restart itself.)
The only thing that I can access with the tablet is Download mode.
P.S: I did realize that in the C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Stock, There in no recovery stock.img in the folder which I suppose that's why my tablet won't boot to stock recovery.

Welp, solved by trying to flash twrp using odin and try to boot to bootloader from there, it seems like my fastboot mode was restored when i do that, and I restored to stock when fastboot is available. admin can you please delete this thread.
Thanks.
P.S: Gosh I'm stupid :'(

Need help fixing my bricked phone

Hey Guys,
I have a redmi 3s prime and i tried to install lineage os on it, during the process i accidentaly flashed twrp over both the recovery and the boot. Now i cannot get into the recovery (and fastboot) unless i flash it over boot before rebooting my phone. After that i AM able to flash an new rom but it seems to always have wifi issues.
atm i am trying to flash the xiaomi developers global rom to see if it makes any difference. My main goal is to flash TWRP and a curstom rom (linage or resurrectionremix).
Can anyone help me?
Thanks alot!
Update #1
The flashing of the global developer rom worked and the wifi seems to work aswell, i will try to boot into fastboot and recovery.
Update #2
Its seems i am able to boot into fastboot and recovery again
Update #3
Following a tutorial for flashing TWRP and a custom rom but cant se2 anyone help me here?:
Code:
>>> Check then next step to root :
- launch minimal adb tool (previously installed)
- type : adb devices (to list phone connected) it will appear "unauthorized"
- on the phone : accept the computer
- re type : adb devices
it has changed in "authorized"
- type : adb reboot bootloader
it will go in fastboot mode (the same that power + vol down)
- type : fastboot devices
your phone will appear as in adb mode (unless the bad signed driver is choosen in win10 ; i won't repeat it again)
- type (optional) : fastboot oem device-info (to verify if bootloader is locked or unlocked)
now, we go to root
- type : fastboot boot twrp.img (if it is your renamed twrp copied in the minimal adb folder)
link for TWRP guide at the end if needed
!!! it will boot temporary in this recovery but it will keep your original recovery !!!
> allow to modify system (don't keep the "read only" if you want to root or flash recovery later)
go to settings to set date, hours, language, set custom options...
My optional advices :
- save your EFS & persist partitions or all whole partitions (except cache) to make a backup
- export this backup in computer or SD card in case of future problem
(EFS, persist are usefull to save and restore your IMEI in particular)
- you can flash directly TWRP with fastboot command : fastboot flash recovery twrp.img
>>> Root :
Now flash DM-verity patch, then superSU.zip to root and accept to wipe dalvik/cache after, finally reboot !
Device is rooted ! and you have kept the original recovery.
the reboot is quite long like rom update (because of cache rebuild)
sometimes, parts of theme are lost after rooting : just restore your theme
some devices don't need DM-verity patch as explained upper
superSU app shows "systemless root" from android 6+, it is normal, read below
>>> Change the Recovery by TWRP (optional) :
Now you are rooted, you have 2 methods :
- Install one TWRP app with googleplay and flash recovery through app on rooted device.
New official app in development (flash/backup .img & .tar)
- OR reboot in fastboot mode (with TWRP app method or power+vol- method or adb reboot recovery method)
in fastboot mode, and type commands :
fastboot devices
fastboot flash recovery twrp.img
(be sure your twrp.img is unlocked and correctly copied/renamed in minimal adb folder)
Now, long press power to turn OFF phone
power + vol+ (release power at vibration) to enter in TWRP or by TWRP app or Updater app or under Windows with minimal adb reboot recovery command
Note for devices with DM-verity : flashing TWRP needs to have patched system with DM-verity patch before because you will modify system most of time - generally, you don't need to patch again because you have ever done it in previous steps - in case of bootloop : go to fastboot mode, boot in TWRP with command and patch it.
Chainfire has recently modified superSU for android 6+ devices with DM-verity to install root without modify the system : it's called "systemless root". When you flash superSU.zip, it detects automatically android version, cleans old files and installs with appropriate method. Maybe no need to patch boot in this case with DM patch.

fastboot help

I was flashing TWRP
I couldn't boot into system after flashing..
This is what I did:
1. fastboot boot recovery.img
2. Swipe to allow modifications in twrp
3. Flash TWRP installer zip
4. Reboot into partition B
5. Reboot bootloader
6. fastboot boot recovery.img
7. Swipe to allow modifications in twrp
8. Flash TWRP installer zip
9. Then I rebooted into recovery to check if recovery boots and it did.
But afterwards couldn't boot back into system. It was again booting into recovery.
I booted into recovery using fastboot boot, that's why it might won't boot into system. Is there a command to boot into system after above procedure?
Files used: https://m.youtube.com/watch?v=tRcYUMBgvaI
? How to Root Mi A1! Unlock Bootloader, TWRP Recovery ... - YouTube
By Dhananjay Bhosale
Kindly also suggest source of files you used, if you know another working method.

I have the same problem. Meanwhile, flash the stock fastboot images.

Why do you want to have TWRP installed? I am following these steps each month (fastboot ROM was always out sooner than my OTA) without any issues.
1. flash stock ROM via fastboot
2. fastboot boot twrp-3.1.1.img and don't allow system modifications or you won't be able to apply OTA
3. install magisk 15.1
4. reboot to system
If first boot takes more than 2-3 minutes, hold power off button until phones restarts, second start will take the usual time.

I also don't allow any modifications from TWRP, and just boot to TWRP when I need to. I do not install TWRP.
Sounds like you'll have to do a miflash of the rom, then try not installing TWRP and not allowing any modifications in TWRP to system. Just use TWRP to flash Magisk.