So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
doud1998 said:
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
Click to expand...
Click to collapse
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Hazou said:
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Click to expand...
Click to collapse
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
doud1998 said:
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
Click to expand...
Click to collapse
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Hazou said:
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Click to expand...
Click to collapse
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
doud1998 said:
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
Click to expand...
Click to collapse
I meant, in my signature under my post u can find within the link INDEX/GUIDE, ALL Things RAZR I under paragraph/ section E a link to all the firmwares available for the Razr I.
But in this case i will post the full link to the firmware site, here.
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
i tried to flash recovery_signed but i have the error
Checking fs on partition pds...
E:can't repaire partition pds
E:failed to mount PDS partition
doud1998 said:
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
Click to expand...
Click to collapse
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Hazou said:
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Click to expand...
Click to collapse
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
+> i don't have any backup and i can't go to recovery , when it turns on it automaticly stuck to the ap fastboot menu
doud1998 said:
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
Click to expand...
Click to collapse
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
waj3k said:
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
Click to expand...
Click to collapse
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
doud1998 said:
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
Click to expand...
Click to collapse
I know, I just uploaded Deodexed Retail Great Britain ICS:
Here you go. There should be a download icon at the top.
give me the right access (i'm [email protected])
Sorry, forgot to set it to public, should be fixed now.
so now i have to flash the boot.img or what? i'm not really sure what to do with this zip
You need to flash custom recovery and then you can install a zip.
Here is a tutorial on how to use recovery, if you're unsure.
i can't make works neither cwm nor twrp
doud1998 said:
So here is my problem, after trying to install a custom rom on my razr i, i may have broken something in the system
Click to expand...
Click to collapse
may i ask you what u have exactly done to install your "custom rom"?
1. Bootloader unlocked?
2. Custom Recovery installed?
3. How did you installed your rom?
4. Which custom rom?
Related
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
UPDATE:
I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors.
Once again: I am sorry and I hope nobody got stuck due to my mistakes!!!
Some errors here.
random hero said:
fastboot flash bootloader bootloader-mako-makoz10o.img
Click to expand...
Click to collapse
Should be
fastboot flash bootloader bootloader-mako-makoz20i.img
random hero said:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
Click to expand...
Click to collapse
Should be
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
random hero said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Skip this if you dont want your custom recovery to be stock again. :good:
random hero said:
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
Click to expand...
Click to collapse
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
vanmarek said:
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
Click to expand...
Click to collapse
The numbers of radio & bootloader in Factory image itself are wrong
I am sorry for the two "spelling errors". I corrected them, should be all fine now.
I did not notice that the other guide contains information about flashing KitKat without losing all your data...
sometimes it can be hard to keep an eye on all the threads in every detail...
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Onknight said:
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Click to expand...
Click to collapse
there are some stock images with root on android develop or orig android develop.
edit: can use dd command to flash images if u have root.
do dd if=/block of/img
like dd if=/dev/block/platform/by-name/system /data/media/0/download/images/zipextracted/system.img
opssemnik said:
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Click to expand...
Click to collapse
Again sorry for that... updated. Thank you!
"I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors."
I thought it was excellent! Anyone who knows what they are doing in the Command Prompt/Terminal understands that they can hit the Tab key to auto-complete the filename. Its up to them to make sure they are accessing their correct folder/file name, not yours!
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is free, winrar is not.
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
In my opinion 7Zip looks slightly better and it doesn't spam you with that your trial is over every time you open it.
what to do with a custom rom?
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is far more friendly towards archives other than rar and zip formats. it's also the only archive app I've found that will allow you to open a flashable zip or apk and replace files inside (like an icon's image file, for example) without having to actually decompile/recompile either the zip or apk (assuming you don't change too much with either file-type)
mad_zack said:
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
Click to expand...
Click to collapse
whether it's a custom or stock rom does not matter. the procedure will be the same either way
Upgrading 4.2>4.3>4.4 was always a piece of cake with Wug toolkit and never had to reinstall any application.
Keeping my settings and applications was important for me.
Sent from my NookColor using Tapatalk 4
how is this method different from if i just removed the -w wipe parameter?
maverickronny said:
how is this method different from if i just removed the -w wipe parameter?
Click to expand...
Click to collapse
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Confused as to why people take all these steps when its just unlock>flash recovery>Flash update rom of your choice and done. All these threads on the same thing makes no sense and lets be honest its not that hard to keep up with threads if you search extensively prior to making up a thread which at week three of KitKat you should of thought would be up already.
Not flaming anyone just trying to understand the thought process. Mistakes happen I get it but we got to do better especially with so many people destroying their phones over simple things.... Jus Sayin'
hp420 said:
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Click to expand...
Click to collapse
I updated from 4.3 to KRT16O (and later, KRT16S) by omitting the "-w" from the batch file, and I didn't lose a byte of userdata. My bootloader is unlocked, but everything else is stock.
It was so painless, I wonder why I ever bothered waiting for OTAs in the first place.
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.
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Flash latest TWRP first. What happened during repartition?
You can allways acces the eeprom writer through short circuiting the sim card, there are a lot of tutorials, the only way to brick this phone is breaking its hardware
nsakhare said:
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Click to expand...
Click to collapse
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
aniketkuber said:
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
The Dork Knight Rises said:
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
Click to expand...
Click to collapse
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Inonotting said:
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Click to expand...
Click to collapse
Repartitioning will wipe both your system partitions [EDIT: Seems I was wrong?]. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
The Dork Knight Rises said:
Repartitioning will wipe both your system partitions. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
Click to expand...
Click to collapse
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Inonotting said:
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Click to expand...
Click to collapse
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
I think I'm back online
The Dork Knight Rises said:
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
Click to expand...
Click to collapse
OK,
I followed your links and flashed :
First : Repartition to Stock Layout
Then : Repartition to 1.2GB Single System
Strange, after this, I did a normal reboot, it rebooted into my old ROM.
Shouldn't that have been erased after partitioning ?
Anyway,
Then I flashed ; update-XenonHD-08-08-15-signed-.zip
WAIT WAIT .....
as I'm typing, I'm flashing update-XenonHD-09-05-15-signed-cancro.zip,
first ROM in a few weeks that seems to be installing.
Let me check is it really installed .... YEP .... progress
Flashing : pa_gapps-modular-pico-5.1-20150418-signed
Everything seems to be going smooth
OK, for the time being .... all good.
Thanks a lot :good:
If your device cannot boot, flash it thru fastboot mode. See the full detailed tutorial on en.miui.com
Well you can directly flash with miflash even with the extended partition. Just edit the fastboot script (.bat extension with windows) and search for line
fastboot flash system+system1
And then delete system1
Fastboot flash system
And use those script for flashing via miflash