Develop Bugs

[Q] Hardest Soft-Bricked ever seen!!! (Help me plz)

hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!

xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?

graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:

xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?

graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------

xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.

hardest soft-bricked ever seen!!!
anybody haven't idea?

Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:

yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---

Cannot mount /data, can't flash ROMs

Hi guys
My Find7 using LVM and Paranoid ROM had rebooting issues (long time issues). I tried to 'fix file system' and it threw an 'encryption failed ' screen on ROM boot. That happened a few tims so I went into TWRP and attempted NANDROID restore.
That failed with error 225. I cannot after removing LVM install ColorOS 1.2.1i or 1.2.7.i . TWRP says it cannot mount '/data'. ColorOS stock recovery fails too.
Now I can't reflash through Fastboot TWRP
I think I recall fixing this by flashing Clockwork but I can't find a version for the Find 7.
Any help?
Thanks so much!

okay as soon as I published, I had moved through mass mounting coloros 1.2.7i using coloros stock recovery
I flashed and it worked.
Hours of failure prior to this.
Thanks, myself.

For anyone who can't flash recovery and is stuck do this
install fastboot. Google it.
download colorOS 1.2.7i and extract the zip to say the folder FIX
download this oppo find7 stock recovery to FIX http://s000.tinyupload.com/index.php?file_id=00219433653419942379 or use TWRP in its place (change the recovery.img name to whatever your twrp file is called.)
hold shift + right click (windows) in FIX and click open command prompt here
copy each line below and right click and paste line by line
Fastboot oem unlock
flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img

HELP! Can't boot into recovery, goes straight to fastboot

Hi
I had installed NamelessRom along with the unified storage layout. All was working smoothly and then I was getting random freezes.
Only way to avoid was to revert back to stock ColorOs. Now however I have the 48mb problem with the partition. On top of that, I can't boot to recovery, it just goes to fastboot. I have tried running the swaplayout.bat partition tool again, but the phone just stays on fastboot for half an hour at least.
Is there any way that I can install NamelessRom again and see if it recognises the unified layout from the first boot?
Any help would be greatly appreciated. Virtual hugs and beers await...

I had the same problem.
download colorOS 1.2.7i and extract the zip
in adb
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img
if your bootloader is locked
Fastboot oem unlock
here is a stock oppo recovery that will handle colorOS1.2.7.i install. http://s000.tinyupload.com/file_upl...3653419942379&del_id=58779725699588589872&gk=
TWRP recovery to remove LVM
Custom ROMS cause random reboots for me. I'm stuck on coloros 2 beta but that is stable. I really want Nameless LVM unified though.

i have a oppo find 7 a year and since then I did to the root, but today decided to change rom but something went wrong because now he is always the restart and go to the screen of fastboot ? I can do is urgent ...
The rom and I put SlimSaber - find7-5.1.1-20150926 find 7

Hello.
Use "fastboot oem unlock", then flash recovery again and everything should work.
Regards.

Hei kucici a link to donwload please?

Hello. I already have an oppo find 7 for a year and I've root it and changed its rom twice. Last rom was color os 1.2.7 and I've changed it to SlimSabet find 7-5.1.1-20150926 find 7 and all went right but when it was 100% the phone reset and it was like you can see in the picture above.
The problem now is that my pc windows 7 has no conection to my oppo find 7. In the device manager it appears android phone and below alcatel adb interface. I can't do the connection between my pc and the oppo and I can't do the recovery.
I always had smartphones, but as it is the first time I have one with windows os and the first time I do this kind of stuff to an android I'm a bit confused...
My oppo is like thart for two weeks now and I don't know what else to do. I've searched in a lot of foruns, but no one has a solution for my problem. Can anybody help me, please?

THANK YOU
darrenpauli said:
I had the same problem.
download colorOS 1.2.7i and extract the zip
in adb
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
........=[/url]
TWRP recovery to remove LVM
Custom ROMS cause random reboots for me. I'm stuck on coloros 2 beta but that is stable. I really want Nameless LVM unified though.
Click to expand...
Click to collapse
YOU MADE MY DAY...... Thank you so much, everything works again.

How to unroot and relock recovery? (fully revert to stock)

I have unlocked and rooted Nexus 5x and would like to revert back to stock + relock bootloader.
What is the easiest and safest way to achieve this?

download fastboot and fastboot drivers then download latest factory image from here https://developers.google.com/android/images?hl=en and unzip it now you should have 6 files but we are gona use only 3 bootloader-bullhead-something.img radio-bullhead-something.img image-bullhead-something.zip now flash bootloader
fastboot flash bootloader bootloader-something.img then fastboot reboot-bootloader then fastboot flash radio-bullhead-something.img and fastboot reboot-bootloader now unzip the other file and cd into it then fastboot flash boot boot.img fastboot flash recovery recovery.img fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash userdata userdata.img and finaly fastboot flash cache cache.img now start your device and if it boots normaly reboot to bootloader again and run fastboot flashing lock (this is gonna wipe all your data so dont set up anything just make sure it boots)

or just run flash-all

I guess i bricked my only phone....:-/

Okay, so im new to this stuff and still i managed to root the phone and flash RR 7.1.2. But i tried to unroot it and this happend:
I only have access to the bootloader and thats it. No recovery, no ROM nothing....when i start ti, it says that my phoe is unlocked and its dangerous and that the phone will boot in 5 secs but it never does....plz help me..and i wanna know where can i learn about all this stuff...its freaking me out since this the only phone i have.....plz help me..

You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image

TheFixItMan said:
You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image
Click to expand...
Click to collapse
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.

Astitva_ said:
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.
Click to expand...
Click to collapse
Firmware must be the same or newer
See the link in my post above for all the firmware - choose the right one for your region
If you don't know which to choose just use this one
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands are (assuming you know how to use & have fastboot already setup as you have already unlocked the bootloader)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (only flash if newer version of android eg going from nougat to oreo)
fastboot flash bootloader bootloader.img (only flash if going to a newer version of android)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

TheFixItMan said:
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
Click to expand...
Click to collapse
Wasn't trying to go back to stock myself (though I did have to in the end) but this was the only rom I found that worked full stop. Thanks so much for this.