Develop Bugs

[Q] Failed to flash ROM, SGW doesn't boot

Hi everybody,
sorry for bothering you, but I think I might need some help.
I tried to flash ParanoidAndroid (first try ever to flash a smartphone) but failed 'somehow'.
Initial steps to create the problem
Initial Status: Gingerbread on a Galaxy W; Pretty old and pretty messed up
Download the update.zip to root the smartphone => Becoming root worked!
Download ParanoidAndroid
Download Clockwork Recovery
Created backups using Titanium Backup as root.
Copied ParanoidAndroid to the GalaxyWs internal sd card (yes, this was my mistake)
Wipe cach partition => It said, it worked, I don't know if it did
Rebooted phone => all fine
Rebooted into recovery mode applied update from SD-Card=> Selected ParanoidAndroid.zip => ErrorMessage (I think it was something like file corrupt, sorry I'm not sure about the specific words, but it sounded like this is no updatefile or this file is not a valid zip file.
Status of the problem
Bootup shows Samsung Logo
Bootup than shows GalaxyW-Screen Logo
Bootup than shows the android recovery symbol OR directly reboots
When trying to open the recovery menu, every second time I get the message "Updating (...) Installing MultiCSC... Can't access /system/csc/DBT/system"
If opening recovery menu works, I can only acces the internal storage of the galaxy to install an update (tried the paranoidandroid several times, it doesn't work)
When plugging in the galaxy w to my USB port, I don't get an USB storage shown on my 2 laptops (1 "Windows 7", 1 "Ubuntu 14.0?" )
neither odin (4.43) nor Heimdall are able to flash any files.
So, simple question, what can I do next?
-I cannot copy clockworkmod to my smartphone
-I don't know if I can easily overwrite the kernel or the bootloader.
I searched the forum but didn't find a clear solution, so sorry if this special configuration was already asked.
Thanks for your help and best regards
FrankyDroid

FrankyDroid said:
[*]Rebooted into recovery mode applied update from SD-Card=> Selected ParanoidAndroid.zip => ErrorMessage (I think it was something like file corrupt, sorry I'm not sure about the specific words, but it sounded like this is no updatefile or this file is not a valid zip file.
Click to expand...
Click to collapse
Your ROM's download has been cut either by a connection issue or by you, That is why I always have a backup rom in my SD Card. Also For kitkat, make sure you got CWM 6.0.4.5 or higher. Personally i use PhilZ Touch Recovery. It is simple enough for me. And odin recognizes your phone only in download mode. So make sure you go to download mode then plug the phone in. And also make sure while working with odin, unplug all USBs and other phones

Hey MayB4ck,
thank you for the tips, I finally got it running Using Philz Touch Recovery. Works like hell
Best regards
FrankyDroid

Encryption fails??

Hi
Anyone have an idea, why after installing a custom rom eg. blispop/excodus or whatever, after flasjing and booting the first time (whit or whitout gapps) i get a encryption fail . saying this was interrupted and not done....try factory resetting (button at middle off screen, says reset) and doing so don´t change anything, manual wiping also changes nothing...??
I´ve never seen this prompt before and not sure what it exactly means?
It happens after flashing cos official 2.14, with twrp 2.8.7.2 , all flashed just fine and working...in cos.
Flashing custom roms gives no errors and seems fine, it boots to the point where this encryption thing shows up?
Tried fastboot oem unlock, which adb says went ok, but no changes whit this error!
Oh and i merged internal sd when i was in cos 2.14 recovery and it works just fine
thx in advance guy´s

spoonymoon said:
Hi
Anyone have an idea, why after installing a custom rom eg. blispop/excodus or whatever, after flasjing and booting the first time (whit or whitout gapps) i get a encryption fail . saying this was interrupted and not done....try factory resetting (button at middle off screen, says reset) and doing so don´t change anything, manual wiping also changes nothing...??
I´ve never seen this prompt before and not sure what it exactly means?
It happens after flashing cos official 2.14, with twrp 2.8.7.2 , all flashed just fine and working...in cos.
Flashing custom roms gives no errors and seems fine, it boots to the point where this encryption thing shows up?
Tried fastboot oem unlock, which adb says went ok, but no changes whit this error!
Oh and i merged internal sd when i was in cos 2.14 recovery and it works just fine
thx in advance guy´s
Click to expand...
Click to collapse
Had the same issue with CM12 on my Find 7a, eventually had to reflash Oppo's stock recovery which has a SD Mass storage option, toggled this and then the boot was able to complete. I then couldn't use the camera or download as the phone said I had no SD card - corrected by reflashing TWRP and changing to ext3

rniblett said:
Had the same issue with CM12 on my Find 7a, eventually had to reflash Oppo's stock recovery which has a SD Mass storage option, toggled this and then the boot was able to complete. I then couldn't use the camera or download as the phone said I had no SD card - corrected by reflashing TWRP and changing to ext3
Click to expand...
Click to collapse
Thx a lot, but only stock recovery i can find is v1.0 which only has usb mass storage option, been inside this option toggled exit usb mass storage option, but same 0, encryption fails...
do you remember or have a link to recovery you used?
edit:flashed 1.2v and there´s no such option
Thx
Edit again:Lol, after fiddling around with getting non unified storage etc, formatting and flashing sahara tool , i totally forgot about new modem/security update necessary and made by cyanogenmod team, (This will give the encryption fails error else) when flashing nightly with updates all was working great!!
So easiest way to switch between unified/non unified is by installing cos 2.14 and use recovery to chose layout, then flash a cm nightly and all is great.

Hard Brick Nubia z11 mini HELP

Hello friends
I had a problem with the mini z11, I have a hard brick.
I wonder if there is any recovery rom, or if the official serves me.
I can flash by nubia Toolstudio?
the terminal does not turn black screen on or enters recovery, flash a rom confusion mini z9.
I need help please, if you recognize the terminal QHUSB_BULK is hope.
Thank you for your interest, Greetings

Still a little bit early for Z11 Mini...
Did you unlock bootloader, rooted and installed some recovery?

Bricked device nubia z11 mini
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?

pratikbr9 said:
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
Click to expand...
Click to collapse
Just flash twrp from pc and go to recovery
Then mount usb storage and copy the rom.zip and flash it

moha07 said:
Just flash twrp from pc and go to recovery
Then mount usb storage and copy the rom.zip and flash it
Click to expand...
Click to collapse
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.

pratikbr9 said:
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
Click to expand...
Click to collapse
Follow this guide to flash twrp, use the vendor id from below guide
https://forum.xda-developers.com/android/development/recovery-unofficial-twrp-3-0-2-zte-t3550995
Then u flash the rom.
Before flashing the rom, wipe everything expect internal storage and sd card

Need persist.img
Hi,
Have got to know persist.img is corrupt. Hence, flashing is happening but no booting even twrp is not helping. Persist.img is usually found in fastboot img of the rom which helps to install rom in fastboot mode. Kindly do let me know if I can find fastboot.img of Nubia z11 mini.
Thank you

Hello guys,
i have the same brick mode as the op.
The system doesn't recognize the mobile, it only shows it as QHUSB_BULK and it keeps disconnecting.
What are the steps to follow from the pc?
I found somewhere one software called one click unbrick but when i try to install the drivers with it it says that "the system policy has been modified to reject unsigned drivers".
If i can take it to the place where the phone is recognized as a storage from the pc then i can take it from there.
Thanks

Unbrick and downgrade
I once brick my nubia the same way. BUT NOW ITS ALIVE AND WORKS FINE (sulking why didn't I bought the ZUK 2 even though at the time i bought z11mini they were similarly priced)
UNBRICKING:-
ALL you have to do is download the same firmware which was installed prior to the rom to which you downgraded to [ simply put if you had v2.40 running before and tried to install v1.40 then download the v2.40 rom for flashing), once downloaded {USE A PC OR MAC TO DOWNLOAD THE ROM OR ELSE IT MIGHT GET CORRUPT} copy it to the root of an sd card(2gb upto 32gb; sdxc cards may not work), insert the sd card into the phone , then press and hold the power button until the phone reboots, as soon as you see the bootlogo press and hold vol- and power keys simultaneously, you wold boot into nubia recovery now select update from sd card confirm and let it install as soon as update finishes your phone will boot back up normally. [UP TILL THIS POINT NO FILES WOULD BE LOST].
NOW YOUR PHONE WILL BE WORKING AGAIN.
DOWNGRADING:-
YOU DON'T NEED ANY EXTERNAL SOFTWARE FOR THIS
JUST DOWNLOAD THE ROM U WANT TO INSTALL AND PLACE INTO SD CARD AS ABOVE.
TAKE A BACKUP AND SAVE ON A PC, ANOTHER PHONE OR ANOTHER SD CARD{not the same one} OR ANYWHERE ELSE SAFE cause after this everything inside your phone will be DELETED.
BOOT INTO RECOVERY as STATED ABOVE.
-ATTENTION- DON'T install the rom as yet.
FIRST WIPE cache and data.
SECOND- INSTALL THE ROM SIMILARLY AS PRESCRIBED ABOVE.
THE SYSTEM WILL INSTALL AND REBOOT.
ENJOY{but why are you so eager to downgrade your system, i was once as well but after downgrade to lollipop.....nothing......performance was same as on Marshmallow.
ADVICE- for some reason the ota updater never shows any new updates, you will have to download updated roms from nubia website to install using recovery{the app has option to apply local update but it does nothing and gets stuck on nubia logo, u will have to restart your phone after that}, as long as you are installing updates u don't need to wipe data and cache and also your files will remain intact. BUT TO THIS ONLY EXCEPTION IS V2.06, on this you do not need to wipe data and cache but the rom itself will wipe all data on your phone so be careful. :good:

NUBIA Z11 mini is Dead
pratikbr9 said:
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
Click to expand...
Click to collapse
I Have the same problem in my Nubia z11 mini , its already dead only it recognize when it connected to PC as QHSUSB_BULK ,
i have tried to flash through QFIL but no use ,
View attachment 4753025

pratikbr9 said:
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
Click to expand...
Click to collapse
Please tell me how to flash TWRP with this condition my device recognize only QHSUSB_BULK in the device manager ,
NO boot loader and recovery mode

[Solved] Problems Switching Partitions (X9076)

Hello everyone,
I recently did upgrade my phones OS from 1.2.x to 2.1.5i (ColorOS) via flash, not OTA.
Afterwards I rooted it using TWRP & SuperSu.
I did return to Stock Recovery (community. oppo. com/en/forum.php?mod=viewthread&tid=17397&extra= (Sorry, I can't post links yet, you have to remove the spaces between community oppo and com)).
My problem now is, that I want to use the "Switch Partition" option, to unify my phone storage, but everytime I try the phone does only boot into recovery, as I had a custom recovery.
Do I need a newer Stock Recovery Version? And where/how can I update it?
Or is it possible to unify the storage manually and continue using ColorOS?
Thanks in advance for any help,
Carroll

Probably you need a newer version. Try this.

Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser

maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash open gapps pico, but I'm not sure this works

javier.pc said:
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash pico, but I'm not sure this works
Click to expand...
Click to collapse
I did just download and install the PlayStore APK, which worked fine.

maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?

Hello, can you please share the stockrecovery.img for fastboot?

nizohio said:
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?
Click to expand...
Click to collapse
I think it is not necessary to download playstore.apk.
create a folder on your PC (Linux and Mac is your top choice), copy all your downloads in this folder (downloads = custom- rom zip, open_gapps zip, SuperSu zip etc)
next you need ADB (android debugging bridge) on your PC.
connect your smartphone with usb to your PC (usb debugging enabled on your phone- you find it under developer)
boot in recovery ( I assume you got lastest TWRP for your phone installed.)
in TWRP go to WIPE / ADVANCED WIPE --> tick Cache, Internal Storage, Data, System, Dalvik/Art Cache.
With this action you are going to lose all data, except data on your external SD and your OS as well. Common sense dictates to back up your data first :good:
after you swiped go to ADVANCED /ADB Sideload --> Swipe to Start Sideload
open your terminal on your pc and cd in your newly created folder with all your zip goodies.
type
Code:
adb sideload custom-zip
Use tab completion - very handy and you know there are no typos.
repeat this command with open-gapps.zip (beware you have to activate sideload in TWRP again) Caution: Do not reboot between installation of your custom - rom and open_gapps.
same procedure with Supersu.zip and so on.
After successful sideload installation, boot your phone to system. Now you should see welcome screen from Android and you have to do a few more setup steps to enjoy your new OS.

Oneplus 3 do not boot after installing OxygenOS 4.0.2

Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin

Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.

dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.

Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.