Database Info

[Q] Need some help with the 9020a

I have sitting here a Samsun Nexus S from Fido in Canada. From what I can tell that makes it the 9020a.
It belongs to a friend and he really wanted CM7 on it after seeing CM7 on my Nexus One.
I helped him root and unlock the phone along with installing ClockWork Recovery.
I left before getting around to installing the ROM. He downloaded it through the ROM manager. After the phone restarted though he was just presented with the white Google logo and it never moved on.
I am trying to help fix this, but he wiped the sdcard and the backup that was done when ROM Manager did a backup.
Here is the problem though, I have installed about 5 or 6 different recovery ROM's trying to get this to work, even more ROM's themselves.
I have tried combinations of ROM's and recovery ROM's.
All of them end with me staring at a white Google logo.
I have access to fastboot and the recovery ROM still. So I decided to just go back to stock by flashing the partitions from fastboot. Some of them will flash, but others won't. I can flash the cache, but I can't flash the recovery, data, or system partitions. When I try I get
sending 'recovery' (8192 KB).
OKAY [ 1.029s]
writing 'recovery'...
FAILED (remote: Write Fail)
or this for Data
FAILED (remote: Unkown Partition)
or this for System
FAILED (remote: Write Fail)
Any and all help would be greatly appreciated. Right now the phone is basically bricked. I am going to sleep but will check back in the morning. If I left some information out please let me know.

Did you unlock the bootloader?
fastboot oem unlock
Then follow the on screen instructions. I had to do that to flash certain *.imgs. I think it has to do with the security checks....
Sent from my Nexus S using XDA Premium App

Does the white Google logo have a padlock symbol at the bottom of the screen? If not then the bootloader is locked. What root method did you use?
Sent from my Nexus S 4G using xda premium

And also what were the commands you used to flash the images.

Sorry for the late reply. Some stuff at work blew up and kept me out late.
atrixboy:
Yes, the bootloader is unlocked.
Rem3Dy:
Yes, there is a pad lock at the bottom of the screen.
suksit:
The commands run originally was just to unlock the phone (fastboot.exe oem unlock). The phone was then rooted and the OS was launched. Once in the OS RomManager was downloaded and installed. Through RomManager clockwork recovery was installed. After that CM7 was selected as the Rom to install. The phone rebooted, did its thing in recovery, then booted to this black screen with white Google logo which I have yet to get passed.
Since then though I have flashed several different recovery images trying to get this to work, right now the recovery is: CWM-based Recovery v4.0.1.4
If I install a Rom from zip through the recovery it says it was OK, but I still get the white logo and nothing else on boot.
I have been trying to just flash boot and system images at this point and am having no luck.
When I try the following:
C:\1>fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.032s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.039s
C:\1>fastboot.exe flash system system.img
sending 'system' (151459 KB)...
OKAY [ 19.073s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.078s
C:\1>fastboot.exe flash data data.img
sending 'data' (4 KB)...
OKAY [ 0.002s]
writing 'data'...
FAILED (remote: Unknown Partition)
finished. total time: 0.032s
If I boot the recovery and go into adb and try and mount the same 3 partitions I get the following:
mount /system - works fine
mount /boot - mount: can't find /boot in /etc/fstab
mount /data - this one runs for like 5 minutes and then fails with the following error: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
I just realized that there is some more information on the screen of the device while in fastboot and I try this. When I try "fasboot.exe flash boot boot.img" I get the following on screen:
Exceed blocks 0x00000020 > 0x0000001e (The exact number of zeros may be wrong, hard counting them at that size)
FASTBOOT STATUS - FAILWrite Fail
Fastboot also indicates at the top of the screen: FASTBOOT MODE - NO BOOT OR RECOVERY IMG
I am able to get into the recovery though...
Not sure what other information to include.

I have run out of ideas. Does anyone know where else could I go and get help with this?

are you flashing *.img files in cwm or bootloader mode?

In fastboot I am flashing .img files, from CWM I am trying to flash .zip. I downloaded a nandroid backup and tried restoring that from within CWM with no luck.

try formatting all memory locations except sd card in "mounts & storage" and fix permissions and then flash img files.

What exactly do you mean by "fix permissions" ?
Edit: Stupid question, found it under advanced.

So I formatted each of the partitions, did the fix permissions option, and then booted back into the bootloader and tried to flash the system.img file with fastboot. It failed.
C:\1>fastboot.exe flash system system.img
< waiting for device >
sending 'system' (151459 KB)...
OKAY [ 19.001s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.006s
Thank you in advance for trying to help, I really appreciate it.
Edit: I just realized at the bottom of the bootloader after trying to flash the system.img file it now says in bold orange text:
Invalid Magic Code! 0x00000003

When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.

did you try this? http://forum.xda-developers.com/showthread.php?t=884093

litanyoffail said:
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
Click to expand...
Click to collapse
I can mount:
/sdcard
/system
/cache
When I try and mount /data it takes 15 minutes and then fails. Says: Error mounting /data!
The model is most definitively i9020a, I just checked under the battery. Thanks for telling me where that is.

milesman said:
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
Click to expand...
Click to collapse
I did, but I am trying it again now.

So, I tried that Nandroid backup again, and it says MD5 mismatch. I checked the MD5's myself and they match. The ones listed in the MD5 file, and the files match.
I tried flashing the *.img files from fastboot, and get that failed to write message I posted earlier.

install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...

milesman said:
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
Click to expand...
Click to collapse
Did this, still having the same problems.

Possible the bootloader unlock corrupted guys? Sounds to me like either a bootloader error else the nand may have died. Unlikely but possible. I read somewhere about loading a custom bootloader to the Nexus S. Maybe try looking for that, I know it was here on XDA, only place to get good help IMHO. The orange error codes are generally related to a corrupt bootloader/bad nand chip to the best of knowledge, feel free to correct me if I'm wrong.
Sent from my Nexus S using xda premium

If the nand was shot, data, SD and system wouldn't mount either. I had a busted nand on my nexus last month, had to send it in.
Seems like the bootloader is unlocked, but acting as if it is locked. Do fastboot devices, make sure the numbers match on your screen and your command prompt.
Something I noticed: If the fastboot flash recovery is failing, how did you get the multiple recoveries on prior to posting here?
Sent from my Nexus S

Trying to flash custom Rom ends up in clockworkmod to reboot...

Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????

xtrg said:
Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????
Click to expand...
Click to collapse
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?

Hey my friend thnks for the reply. I'll try all of these right now. If u can please follow the thread, I might have more questions...Thnks again!

I've reache the point where i mount again my sd card and making all thw wipe things...
I' ve installed the rom but after it says that is succesfully installed and rebooting it shows the htc logo and after that...nothing!
The device turns off(or at least i think it is)black screen, no charge little orange light...But when it comes to this mode, I can hear the soun of the pc like when u do connect a device!
What am I doing wrong?
And yes I have hboot 1.14. What is the correct sequence in the actions????

Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app

exad said:
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?
Click to expand...
Click to collapse
exad said:
Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...

xtrg said:
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...
Click to expand...
Click to collapse
You're wiping after flashing the boot.img... so you need to reflash the boot.img don't wipe anything, just fastboot flash boot boot.img and then reboot the phone.

[Q] How long does it usually take to flash 10MB stock recovery?

HI there. I want to update the latest OTA for UK (bought my phone from amazon.co.uk)
So I downloaded Blur_Version.174.44.9.falcon_umts.Retail.en.GB kitkat version since I have 4.4 and extracted it and tried to install stock recovery over not working TWRP. So I did fastboot flash recovery recovery.img
This is what I see in windoze terminal:
Code:
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.375s]
writing 'recovery'...
This is what I see in fastboot:
Code:
cmd: getvar:partition-type:recovery
cmd: getvar:max-download-size
cmd: download:00a00000
cmd: flash:recovery
What could be wrong with not properly installing stock recovery?

Where can I get stock recovery for xt1032 bought from amazon.co.uk running kitkat?
I have no problem installing TWRP (which is buggy in my case and has not features of backing up or restoring).

It happens the same with Blur_Version.14.71.8.falcon_umts.Retail.en.GB jelly bean version.
Any ideas where I can get stock recovery for xt1032?
Found one here: http://forum.xda-developers.com/showthread.php?t=2616399
However I get the same as with previous ones:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.378s]
writing 'recovery'...

Hmmm...no solution for your problem atm.
But you'll find the stock recovery in the zip you've downloaded.
So just extract recovery.img
....maybe something ist wrong with the partition.
If you want you can try to erase it:
fastboot erase recovery
Click to expand...
Click to collapse

mokkami said:
Hmmm...no solution for your problem atm.
But you'll find the stock recovery in the zip you've downloaded.
So just extract recovery.img
....maybe something ist wrong with the partition.
If you want you can try to erase it:
Click to expand...
Click to collapse
If I erase partition, will fastboot flash recovery recovery.img recreate it? Or do I have to create it by hand before I try to flash new recovery?
Sent from my XT1032 using Tapatalk

frojnd said:
If I erase partition, will fastboot flash recovery recovery.img recreate it?
Click to expand...
Click to collapse
Yes

mokkami said:
Yes
Click to expand...
Click to collapse
I tried and it's the same. I can't flash stock recovery. It hangs at
Code:
writing 'recovery'...
So for me as I have rooted, unlocked bootloader and encrypted. The only solution for installing newst update that fixes loss of signal is to:
1) factory reset my phone -> loose encryption
2) try to install stock recovery afterwards?
or:
1) Follow this guide for installing stock recovery http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
which will also have stock recovery or not? And do I have to factory reset before I perform this (due to my phone being encrypted) or not?
Doesn't factory reset needs working recovery?

With awesome user on @freenode, awesome user @utkanos helped me with ditching /data by making f2fs file system:
1) go to recover (in my case broken TWRP)
2) adb shell (from OS)
3) mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata (from OS)
All done. Reboot and you are out of encryption and all user data and apps. Will try to flash stock recovery now.
edit1: tried to flash it with fastboot command but it hanged like in all previous attempts. So I installed OTA even thoug I had philz recovery. The effect was like that that it went to philz recovery and wrote about this signature is not ok.... I taped ignore and it did go to a ahalf of bar progress and then just rebooted and went into system. After couple of seconds it just rebooted and the procedure repeated itself.
edit2: Managed to flash it with mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
FINALYY! And then it installed update properly 176.44.1.en.GB rooted, unlocked

Root: Stuck at "Your device is booting now"

Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!

if you have the boot backup then restore it.

venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.

if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip

I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img

Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).

Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery

Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.

V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.

venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.

Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.

Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone

question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.

[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now

nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).

Help, going back to stock EMUI 5 and bricked

Guys, I wanted to go back to EMUI 5 stock (BLN-L24C567B366) but I got stock flashing the BOOT, RECOVERY, and SYSTEM images, fastboot shows
Code:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (15508 KB)...
OKAY [ 0.594s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.620s
I looked up for that and seems because the PC is not communicating with fastboot maybe due to drivers or disabled USB Debugging, what can I do to recover my phone? My bootloader is still unlocked and shows
Code:
PHONE Unlocked
FRP Lock
I still have access to TWRP if that helps... Help please :crying:

Jessooca said:
Seeing as you have twrp still working, why not reflash any of the other custom roms so you have a working phone again? I'm assuming you still have whichever rom you been using, on your phone again? If not, put one on an SD card then put the sd card into the phone, reboot twrp back into recovery so it can find the rom on the sd card and flash that rom.
Click to expand...
Click to collapse
Thank you very much, I will download a ROM now bcz I just had root.
Jessooca said:
Then instead of going back to stock via cmd and fastboot just copy over the update file in the dload folder and do the 3 button restart so it can detect the update file and restore your phone.
Click to expand...
Click to collapse
With this you mean getting all the files out of update.zip(Full-OTA) and putting them in dload folder in the sdcard right? I tried that(just without any system installed ) and it failed at 5%, is there a difference?
Again, thanks a lot for your help