Related
I am stuck without recovery i accidently lost it while trying to flash another recovery..now my phone doesnt boot..so is there any other way to flash recovery without rooting again..i tried flashing it via fastboot but im using hboot 1.33.001d so cant flash anything there...as the verification fails..can does anybody have an idea how to skip the signature verification..
As written in this thread you can flash the
orange-xxx.nbh via fastboot, then boot the rom and you have a full engineering SPL installed. From there you can continue as you want, i.e. flashing new recovery, new SPL, new rom, etc.
which firmware will i get after flashing this..and fyi i am using g1 us version..
I just thought of one other thing to try first. Install Android Commander on your PC. I have successfully reflashed Amon RA recovery with the new radio/SPL from there - there's an option to flash a recovery from your hard drive.
http://androidcommander.com
Failing that, you'll need to start with the nbh, then flash radio/spl/recovery using the instructions provided by Ezterry for installing the radio/spl.
Khizzer said:
which firmware will i get after flashing this..and fyi i am using g1 us version..
Click to expand...
Click to collapse
It's a frensh one, but you will not boot into it, because you'll boot directly into bootloader/fastboot. It's only needed for the engineering spl.
Sent from my Gingerbread on Dream using XDA App
all you do is flash the orange nbh so than you can wipe recovery and flash new one... than you want to flash your radio(2708/2825) than flash spl pretty simple and very convenient lol was in same situation couple days ago
sisterchick said:
I just thought of one other thing to try first. Install Android Commander on your PC. I have successfully reflashed Amon RA recovery with the new radio/SPL from there - there's an option to flash a recovery from your hard drive.
http://androidcommander.com
Failing that, you'll need to start with the nbh, then flash radio/spl/recovery using the instructions provided by Ezterry for installing the radio/spl.
Click to expand...
Click to collapse
i already have it but it does recognize our device if it is on i tried this procedure but of no luck so im back to the nbh method..
does the nbh flashing take a long time...
na it doesn't take long at all it really easy.... you are doing the orange nbh right?
do you have fastboot drivers set up? because you need those... lol
can you still boot up your phone? cuz if you can, what you do is go to rom manager and flash the CWM recovery from that
ldrifta said:
na it doesn't take long at all it really easy.... you are doing the orange nbh right?
Click to expand...
Click to collapse
yeah its about half an hour and its not yet over yes i am doing orange nbh..
bluizzo said:
can you still boot up your phone? cuz if you can, what you do is go to rom manager and flash the CWM recovery from that
Click to expand...
Click to collapse
no my phone doesnt boot up..
ldrifta said:
do you have fastboot drivers set up? because you need those... lol
Click to expand...
Click to collapse
no idea about the fastboot drivers i just diconnected usb and now cmd says that status read failed <too many links>>
so you dont know if you have fastboot setup on your pc...?
yeah i think so but i use android commander and everything via usb..
and yes it was about 30 mins i waited nothing happened..
it says verification failed i attached an image of that
ok power off the device and reboot to fastboot mode, rename the orange file you have located in the sdk/tools folder to 'orange.nbh' now get to the fastboot cmd and type 'fastboot flash nbh orange.nbh' tell me what happens after that?
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Killa_vatt said:
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Click to expand...
Click to collapse
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
tpbklake said:
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
Click to expand...
Click to collapse
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Killa_vatt said:
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Click to expand...
Click to collapse
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
prunzzz said:
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
Click to expand...
Click to collapse
I have already tried many ways to install many other roms. What will you recommend?
Killa_vatt said:
I have already tried many ways to install many other roms. What will you recommend?
Click to expand...
Click to collapse
what kind of errors did you get when you flashed other roms??
prunzzz said:
what kind of errors did you get when you flashed other roms??
Click to expand...
Click to collapse
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
have you tried flashing through HBOOT??
prunzzz said:
have you tried flashing through HBOOT??
Click to expand...
Click to collapse
That is done by renaming a file to PG98***?
Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
tpbklake said:
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
Click to expand...
Click to collapse
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Killa_vatt said:
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Click to expand...
Click to collapse
OK, after re-reading your posts, here are some additional tips:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
As for trying to flash 10 different RUU's there ERROR 131 indicates that you have a bad goldcard.
Killa_vatt said:
That is done by renaming a file to PG98***?
Click to expand...
Click to collapse
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Also consider what tpbklake said
HIT THANKS IF I HELPED YOU
tpbklake said:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
prunzzz said:
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Click to expand...
Click to collapse
I mean PG32IMG,forgot that.
I fully wiped everything.
I did not flashed rom's boot.img,thanks! Gonna try it later.
tpbklake said:
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
Thank you very much! I feel dummy now =)
Flashing rom's boot.img fixed all problems. Most of roms works now. Thanked everyone in topic.
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup
abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....
heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.
Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Tyche303 said:
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Click to expand...
Click to collapse
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
KevMetal said:
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
Click to expand...
Click to collapse
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Tyche303 said:
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Click to expand...
Click to collapse
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
Awesome, thanks! I will try that later tonight or tomorrow.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
So I downloaded a fastboot file from here :https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
The miui flash program wouldn't work for me. On the website you linked me there was a method that used twrp to flash it. But when use twrp I can't see any of the zip files in twrp. I've tried three different ones from the link I just shared here. Not sure what the problem is.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
nevermind, I have gotten it to work. Thank you for your help
Tyche303 said:
nevermind, I have gotten it to work. Thank you for your help
Click to expand...
Click to collapse
okay glad you came right
half the fun is figuring this stuff out