Related
I have downloaded the app from eclips3 and have tried rooting my phone..when i go to reboot my phone and holding down vol down plus pwer key my phone does not read the PB00IMG.zip file, eclips3 has been a lot of help but we have ran out of ideas. Does anyone else have any ideas of how to root my phone or put a ROM on it?
1. try a new sd card
2. make sure you have at least 50 % battery life...
3. Re download the image..
if not...go to verizon n tell them you cant root your phone.. LOL! jk...
hope someone else knows what to do...
lol thanks..do you think verizon will help me root it?? lol jk;-)
do you have the PB00IMG.zip in the root of your sd card (not in any other folders?)
The Beginning
You are going to need the Android SDK installed and working as we all the latest version of Java.
Extract and run ‘SDK setup.exe’ . You can find a quick setup on the download page for Android SDK.
Make sure you install the SDK for 1.5, 2.1 and USB Driver package (to make it easy just click to install all).
Put your phone into USB debugging mode: Settings > Applications > Development > check USB Debugging
Connect your phone to your PC
Open device manager on your PC, the device with the yellow exclamation mark next to it is your phone.
Right click on the device and click ‘Update Device’. Find and locate your Android SDK directory and find the ‘USB Driver’ Folder. If you can’t find the USB Driver folder then you didn’t install the USB Driver Package.
Once your Device driver is updated you can continue on to the next step: Rooting your phone.
Rooting Your Phone
Download PB00IMG.zip
Place PB00IMG.zip into the root directory of your SD Card. (Thats right inside your SD Card, not inside any other folders.)
Power down your phone.
Turn your phone back up by holding down the ‘down volume’ and the power on keys at the same time. It should bring you to the HBOOT screen. When it says Push Activate you have to push down on your trackball. The process will take about 10 minutes, and when your phone starts back up it will take quite a bit longer than usual.
Your Phone is now rooted!! (That was the easy part)
Install Recovery Image
Be sure your phones SD card is not mounted to your computer before you start anything.
Download Recovery.zip
Extract file contents to your \tools\ directory of your Android SDK.
Open up a command prompt and go to your tools directory (‘cd …./android-sdk-windows/tools’ or where ever your directory is but cd is the change directory command) , and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
You now have a recovery partition on your phone, you can access it by going into recovery mode on your phone (volume up + power on).
Install new rooted ROM
Download eris21official-root.zip
Copy eris21official-root.zip into the root directory of your SD Card.
Reboot your phone into Recovery Mode. (power down your phone and turn it back on with volume up and power button)
Go to Wipe, and do a wipe of data/factory reset, as well as dalvik-cache wipe.
Go back to the main menu and select “Flash Zip from SDcard”. You should see your eris21official-root.zip, select it and press the track ball to flash it.
You are now done and are running the latest version of the root rom. Remember these last step because they are the steps you will be using to use other ROMS or to update.
Click to expand...
Click to collapse
if you follow those steps step by step then it should work... its exactly what i did and what a lot of other people have done
for custom roms just find the rom you would like to try and follow the 'install new rooted rom' steps
i have downloaded and set up the sdk but i dont have a yellow triangle with an explanation point on my device manager..my phone is in debugging mode. I have just tried over and over copying the PB00IMG.zip file to my sd card and it still doesnt read it. It just says trying to read image PB00DIAG.img and a few others and says no image then goes straight to the hboot screen.
naenaek22 said:
i have downloaded and set up the sdk but i dont have a yellow triangle with an explanation point on my device manager..my phone is in debugging mode. I have just tried over and over copying the PB00IMG.zip file to my sd card and it still doesnt read it. It just says trying to read image PB00DIAG.img and a few others and says no image then goes straight to the hboot screen.
Click to expand...
Click to collapse
I'm rooting right now (my third Eris, actually) and it does that. You need to agree to updating by pressing volume up or down (don't recall which one, the screen will tell you, though..). It looks like it wants you to run through the first step all over again but it's not, the second time is the actual installation of the .zip on your sdcard.
-mak
it says my drivers are up to date when i click update drivers...so now i am stuck trying to root my phone..the problem i am having there is i cant get my phone to read the PB00IMG.zip file from the hboot screen.
lg optimus s
can this phone be rooted
tlove008 said:
can this phone be rooted
Click to expand...
Click to collapse
First, this post doesn't belong here as this is the HTC Droid Eris forum. Your phone isn't even an HTC brand. I looked and saw that XDA doesn't have a section for an LG Optimus S so I would guess not, personally. Perhaps you should try Google?
Good luck.
I've tried about a million times now and can not get my Gtab into clockwork recovery. I downloaded the internal version of clockworkmod and hooked my gtab up to the computer and placed the clockworkmod zip in the recovery folder and unzipped it. Then I turned my device off and held down the power button + vol + it then says "Recovery key detected" and acts like its installing. Then It reboots and I turn it off again and it just keeps doing the same thing saying "
recovery key detected" and won't boot into clockwork!!!! Advice please?? And I know this is a noob question, I do. I tried following the instructions on the stickies but they're vague as to which clockwork zip I am to download??? Please help. Thanks!!!
From what I gather, after you download the internal zip you unzip that so you see the update.zip file & recovery folder. You move both of those to the root of the g-tab which would be /sdcard. I haven't done it yet since mine is charging right now.
Trying it now
GOLDEN....Finally! Thank you sir!
peurifoyd said:
I've tried about a million times now and can not get my Gtab into clockwork recovery. I downloaded the internal version of clockworkmod and hooked my gtab up to the computer and placed the clockworkmod zip in the recovery folder and unzipped it. Then I turned my device off and held down the power button + vol + it then says "Recovery key detected" and acts like its installing. Then It reboots and I turn it off again and it just keeps doing the same thing saying "
recovery key detected" and won't boot into clockwork!!!! Advice please?? And I know this is a noob question, I do. I tried following the instructions on the stickies but they're vague as to which clockwork zip I am to download??? Please help. Thanks!!!
Click to expand...
Click to collapse
Hmm?.. I think the issue you are having is moving the update zip into the recovery folder.
when you extract the files from the zip file extract them to the main directory "/SCARD" and thats it.
After you extract it you should see (in that directory) a folder that says "Recovery" , within that folder there should be a file named "Command" and thats it, no more files in there.
Also in that main directory you should see an "update.zip" file, leave it there. DON'T MOVE IT into the recovery folder.
from there follow directions to boot into recovery mode.
1) Power down
2) Press and Hold down volume up + rocker
3) Press and hold Power Button
4) when device powers on you will see "Recovery Key Detected"
5) release buttons
6) recovery will install and reboot as normal.
7) Power down and follow steps 1 through 5 again.
8) You should be in recovery mode now.
Edit:
Took too long to make this post!! LOL
my noob questions...what version did you use and can you post a link to it?? i am getting my g tab today!!
thx...
Follow the instructions on this link.
http://forum.xda-developers.com/showthread.php?t=865245&highlight=clockwork
Rumbleweed said:
Follow the instructions on this link.
http://forum.xda-developers.com/showthread.php?t=865245&highlight=clockwork
Click to expand...
Click to collapse
thx. i'm up n runnin vegan 5....
Tekrhino, I feel stupid but I have to ask for your help re: this same issue. It seems so clear on what to do from your instructions but I still can't get clockwork recovery to load. I'm having the exact same issue of not getting into clockwork recovery so I must be doing something wrong.
Maybe by telling my steps you can get me on the right path.
1. Downloaded clockwork mod to desktop.
2. extracted update.zip now I have a file that says update unzipped.
3. attached gtab to usb, recognized by computer as removable disk.
4. click on "open folder to view files and see list of different files on gtab
5. copy and paste recovery and update unzipped to this window and disconnect gtab from computer and then try to do the above mentioned steps to get into recovery. get the recovery key is detected message but can't get into clockwork recovery.
I must be doing something wrong but can't figure out what! Any suggestions that can point out the error of my process will be very much appreciated.
GGGwhatever!!
You don't need to unzip update.zip. You just put it in the /sdcard directory and the reboot to CWM and take the CWM options to run it.
Rev
Download CWM to your computer.
Uncompress it get two files (recovery and update.zip) Do not unzip update.zip
put these two files in your root directory on your Gtab ( SDCARD)
Hold Vol+ button turn on.
Sit back and watch
GGGTABBB! said:
Tekrhino, I feel stupid but I have to ask for your help re: this same issue. It seems so clear on what to do from your instructions but I still can't get clockwork recovery to load. I'm having the exact same issue of not getting into clockwork recovery so I must be doing something wrong.
Maybe by telling my steps you can get me on the right path.
1. Downloaded clockwork mod to desktop.
2. extracted update.zip now I have a file that says update unzipped.
3. attached gtab to usb, recognized by computer as removable disk.
4. click on "open folder to view files and see list of different files on gtab
5. copy and paste recovery and update unzipped to this window and disconnect gtab from computer and then try to do the above mentioned steps to get into recovery. get the recovery key is detected message but can't get into clockwork recovery.
I must be doing something wrong but can't figure out what! Any suggestions that can point out the error of my process will be very much appreciated.
Click to expand...
Click to collapse
I just got my tablet today and am still playing around with the stock, but from what I read I think your mistake is unzipping the "update.zip" file.
You only unzip the clockwork mod file you downloaded. Then you have two files: 'update.zip' and 'recovery' (folder). Leave the update.zip alone, don't unzip it and put these two files onto your gtab. Either internal storage (sdcard) or microsd card (sdcard2), depending on which clockwork file you have.
Thanks Rev! I know it is something simple but it was what I needed to get started.
Now I can play!
Newbie possible screwup
Help, followed install for Cwd and all get is the recovery reconized and it just stays on theviewsonic open page. Willnot go any further it is stuck.
I messed up the G Tablet soon after receiving it.
Here are two links with information on how to get it restored.
Viewsonic GTablet For Dummies
Guide - Restore G Tablet after a failed Recovery Mode update
Hope this helps.
djab67
(If I have helped, please hit the "Thanks" button)
I am trying to get my viewsonic g tab back to factory. I installed the APX driver ok, and downloaded the applicable files. I try to run the nvflash_gtablet.bat script and it comes up with a file configuration error that the file can't be found. I am running windows 7. Any suggestions?
i have never done nvflash and never got brick and loaded multiple roms and went on dif dev branches
this is for 1.1
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
and this is for 1.2
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4349-user.zip
rename the zip file to "update.zip"
hopefully you partioned your tab before nvflashing it. if not then please ignore this.
put update.zip in root of your sd card.
create a folder named "recovery" and place an empty file named command with this text inside
Code:
--update_package=SDCARD:/update.zip
then go into recovery and let it update.
hope i helped somewhat
ps to make files in win 7. i open notepad and paste code then save a command.tmp then i go and delete tmp. it leaves it as a file. and works
Jrome86 said:
I am trying to get my viewsonic g tab back to factory. I installed the APX driver ok, and downloaded the applicable files. I try to run the nvflash_gtablet.bat script and it comes up with a file configuration error that the file can't be found. I am running windows 7. Any suggestions?
Click to expand...
Click to collapse
h i because you didn't have the image files to flash into. This is probably the most common mistake that beginners make.
Go to my website linked in my signature and go to the start here page. You're probably a code yellow.
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
the best way using complete firmware (containing stock rom) like this version UL-K017-WW-11.2.3.18.2-user, if succeed then later on you can continue with OTA system update
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
So awesome you figured this out! Glad it worked out for you and I'll be saving this in case I find myself in the same boat. Thank you for this!!
Sent from my Nexus 6
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
2. Extract (archive in archive) and throws to the SD card. Rename the file to K017_sdupdate.zip and Insert the flash drive into a tablet. (Use good one SD card)
Click to expand...
Click to collapse
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
WeAreNotAlone said:
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
Click to expand...
Click to collapse
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
sevensvr said:
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
Click to expand...
Click to collapse
RE: boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder ???????
Having some progress, renaming ifwi.zip which contains (4) bin files when Recovery was selected caused the robot with the Updating System Settings to appear, but a couple of seconds later it said ERROR with the robot laying on it's back, then it exits. Device reboots as normal.
To clarify:
WW_V11.2.3.28.zip download from ASUS was extracted with a Windows computer,
WW_V11.2.3.28.zip extracting /creating following folders, files, then the contents were copied to the ROOT of a MicroSD card formated Fat32
1: boot.img, fastboot.img and splashscreen.img (TO ROOT)
2: ifwi.zip to ROOT. (contains (4) bin files, is this supposed to be extracted to I assume folder by same name off root? OR does this ZIP file just get renamed?)
3: System folder
4: Recovery folder
5: META-INF folder
I do not see a flashtool/fasboot folder. (Fastboot, right?)
Q: Is boot.img, fastboot.img and splashscreen.img supposed to be in a folder named "Flashtool" OR are they supposed to be in folder named "Fastboot" with a pathway of Root (Drive) D:/Flashtool/fastboot ?
.
(NOTE ALL OF THIS IS BEING DONE ON THE DEVICE ITSELF, with contents on SD card.)
Still getting the ERROR! message wit the Adroid robot that is laying on his back.
The zip file that extracts from the main zip WW_V11.2.3.28.zip is named:
ifwi.zip...
I have left a copy of it in the ROOT, plus copied it and renamed it to
K01A_sdupdate.zip
K017_sdupdate.zip
LEAVING COPIES OF ALL IN THE ROOT OF THE SDCARD.
Q: If more than (1) zip is present does this confuse fastboot? OR does fastboot automatically look for zip zip which matches model ID of device? (K01A)
I have left copies of boot.img, fastboot.img and splashscreen.img in the ROOT of the drive.
AND
Created: (ROOT) flashtools/fastboot with *img files in it.
Created: (ROOT) fastboot with *img files in it.
Copied the *img files to under "Flashtools" folder in flashtools/fastboot.
Figuring all the bases would be covered. (EG: *img Files in ROOT, files in Flashtools, Flashtools/fastboot, and a folder named fastboot as well.
Q: I've noticed on the SD card files appearing that previously were not there, when the flash aborts is there some kind of file or files you need to delete, or is it ok to leave the newly generated files there?
---------- Post added at 03:43 AM ---------- Previous post was at 03:37 AM ----------
Deleted:
ifwi.zip.
K017_sdupdate.zip
Tried:
K01A_sdupdate.zip
Still getting robot on it's back with ERROR!
who said you need to renaming ifwi.zip, What you need is read all instruction carefully,
do not put more than 1 zip file in SD card only firmware file which is already renamed to K017_sdupdate.zip, and use good brand SD card.
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
commando987 said:
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
Click to expand...
Click to collapse
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
My Asus MemoPad ME170C has risen again!
sevensvr said:
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
Click to expand...
Click to collapse
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
sevensvr said:
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
Click to expand...
Click to collapse
Installing bar not complete at the end but not give error and restart. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
mapagmatyag said:
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
Click to expand...
Click to collapse
you welcome friend
commando987 said:
Installing bar not complete at the end but not give error and restart it. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
Click to expand...
Click to collapse
it seems the tablet didn't read your SD card, to assure SD card problem when the robot appear while system update press buttom vol + and - rapidly to show installing status.
if the tablet didn't read ur SD card try to use another SD card
BIG Thanks
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
mnabarro said:
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
Click to expand...
Click to collapse
happy to heard it
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
mashton70 said:
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
Click to expand...
Click to collapse
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
OK, I finally got the usb drivers working on my computer and made it through all commands which is much further than I was getting before.
I got to step 8 "Disconnect the USB cable and select the SD update or Recovery" and selected "Recovery" in DROIDBOOT (I don't have an "SD update" option there) and after like 1 second of "installing system updates" I get the android falling over guy error and then it hangs on the asus splash screen for ever.
download ME70CX for ME170CX
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
ydobon.999 said:
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
Click to expand...
Click to collapse
That did it!
I used the firmware ME70CX and renamed the file "K01A_sdupdate.zip" and followed all of the other steps as per the original instructions and got my ME170CX working again but for one problem. . . I was still getting the "demo has stopped" error! So I proceeded to attempt root again, this time with RootZenFone-1.4.6r and and now it's working perfectly and rooted as well!
Many thanks to all!!
EDIT: The latest update to Newflasher (v52) built in the functionality to keep user data intact as a prompt while flashing.
Version 52 is out!
- version 52 (01.10.2021)
Implemented userprompt for keeping userdata, thanks @OhayouBaka for figuring out! Removed bootloader log retrieval
In short explanation all files marked with NOERASE inside update.xml is in relation to factory reset, so skiping files marked with NOERASE preserves userdata while flashing. Thanks OhayouBaka for figuring that out! Now newflasher have yes no promp for keeping userdata or making clean installation with factory reset. Bootloader log is removed since I found nothing usefull there.
Click to expand...
Click to collapse
As some people here who have owned previous Xperia devices may already know, to keep data while flashing firmware in Newflasher, you have to delete the userdata.sin file in the firmware folder.
However on the Xperia 1 III, this has changed.
If you only delete userdata.sin, your data partition will be corrupt and you will be forced to factory reset and lose all your data.
To prevent this from happening, not only do you have to delete userdata.sin, but also appslog.sin, diag.sin and metadata.sin from the firmware folder as well.
Found this by checking the update.xml file in the firmware folder, all required sin files to delete are listed as "<NOERASE>".
Unfortunately I had to learn this the hard way, but hopefully this post will save Xperia 1 III owners in the future from accidentally being forced to factory reset their devices when using Newflasher.
If you need the full instructions on flashing firmware that this guide compliments, check this thread: https://forum.xda-developers.com/t/flashing-a-xperia-1-iii-without-unlocking.4326235/
OhayouBaka said:
As some people here who have owned previous Xperia devices may already know, to keep data while flashing firmware in Newflasher, you have to delete the userdata.sin file in the firmware folder.
However on the Xperia 1 III, this has changed.
If you only delete userdata.sin, your data partition will be corrupt and you will be forced to factory reset and lose all your data.
To prevent this from happening, not only do you have to delete userdata.sin, but also appslog.sin, diag.sin and metadata.sin from the firmware folder as well.
Found this by checking the update.xml file in the firmware folder, all required sin files to delete are listed as "<NOERASE>".
Unfortunately I had to learn this the hard way, but hopefully this post will save Xperia 1 III owners in the future from accidentally being forced to factory reset their devices when using Newflasher.
If you need the full instructions on flashing firmware that this guide compliments, check this thread: https://forum.xda-developers.com/t/flashing-a-xperia-1-iii-without-unlocking.4326235/
Click to expand...
Click to collapse
First of all, thank you very much for this research.
If i understood right, i can update device this way and it will be essentially the same as updating the device via OTA, right ?
DennisDD78 said:
First of all, thank you very much for this research.
If i understood right, i can update device this way and it will be essentially the same as updating the device via OTA, right ?
Click to expand...
Click to collapse
I believe so, all your data, apps, etc will still stay as it was before the update.
OhayouBaka said:
I believe so, all your data, apps, etc will still stay as it was before the update.
Click to expand...
Click to collapse
And all system settings should remain ?
By the way, just wanted to clearify something, you mentioned about update.xml file in the firmware folder, should i edit it somehow before flashing, or just delete those four files from f/w folder ?
DennisDD78 said:
And all system settings should remain ?
By the way, just wanted to clearify something, you mentioned about update.xml file in the firmware folder, should i edit it somehow before flashing, or just delete those four files from f/w folder ?
Click to expand...
Click to collapse
Yeah system settings will remain too. Just leave update.xml alone, dont delete it. Only delete the four files that I mentioned from the f/w folder.
OhayouBaka said:
Yeah system settings will remain too. Just leave update.xml alone, dont delete it. Only delete the four files that I mentioned from the f/w folder.
Click to expand...
Click to collapse
Thank you, dear friend!
Much appreciated to your help. Just flash mine back to latest factory firmware to receive OTA and everything looks fine for now. System settings and installed app data are saved with no problem.
so I had to jump through a few threads to figure out the details on how to update a magisk rooted x1m3 to the latest firmware without wiping(dirty flash). Figured I'd write out the steps here for others benefits
1 - download the firmware with Xperifirm
2 - download newflasher and extract to the firmware folder
3 - delete the following files from the firmware folder for no wipe dirty flash - userdata.sin, appslog.sin, diag.sin and metadata.sin. Skip this step if you're using Newflasher v52 and above
4 - download UnSin and extract to the firmware folder
5 - in the firmware folder, drag and drop boot_X-FLASH-ALL-*.sin into unsin.exe, and it will generate a boot_X-FLASH-ALL*.img in the same folder
6 - copy the boot_X-FLASH-ALL*.img onto your phone's sdcard somewhere.
7 - using magisk manager, install magisk and use the "select and patch a file" method. Select the boot_X-FLASH-All*.img file. This will generate a magisk_patched*.img onto your phone's sdcard
8 - download and extract platform-tools. Copy the magisk_patched*.img file from your phone's sdcard into the platform-tools folder on the computer. Rename the file to simply "magisk_patched.img"
9 - back up the phone(since still no real TWRP and titanium backup has been broken for a long time, I've been using Swift Backup)
10 - shut down the phone, plug in a usb-c cable to the computer, then while holding the volume DOWN button, plug in the usb-c cable to the phone. The LED indicator should be GREEN indicating FLASHMODE
11 - open up cmd prompt, and navigate to the firmware folder from step 1. Type in the following command
Code:
newflasher set_active:a
then hit enter. You should see result like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12 - in windows explorer, navigate to the firmware folder, and double click on newflasher.exe(phone should still be in FLASHMODE). Respond to the prompts - n gordongate, p power off, n trim
13 - wait for the flashing of the new firmware to finish
14 - disconnect the phone from the usb cable, and power it back up. Check and make sure you have all your data/apps/etc. At this point it should boot into the rom just fine, but won't have root access and magisk will show that its not installed
15 - power off the phone again. This time, press the volume UP button while plugging in the USB-C cable. LED indicator should be BLUE for FASTBOOT
16 - open up a new cmd prompt, navigate to the platform-tools folder. Type
Code:
fastboot devices
and hit enter to confirm your phone is connected. Should respond with an alphanumeric number and the term fastboot
17 - type the following commands into cmd prompt
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
18 - DONE. Your phone should be on the new firmware with root and all your data/apps/etc
props to @Miustone, @OhayouBaka, @Forbesii for the original instructions. I just sort of put it all in one place
fingers crossed a great dev will come along and give us TWRP soon!
Does r / o and r / w work in Root Explorer?
Edited the original post to include the info that Newflasher has been updated with this functionality built in.
Hi, is there any way I can unlock the /system partition?
Does this allow us to mount the system partition as R/W?
largo2 said:
Hi, is there any way I can unlock the /system partition?
Does this allow us to mount the system partition as R/W?
Click to expand...
Click to collapse
With root only, i guess.
DennisDD78 said:
With root only, i guess.
Click to expand...
Click to collapse
Hello, of course my Xperia 1 iii is root.
Sorry, I'm using Google Translate
Sure wish there was a delete post button. It's a forum and I can't delete my own posts. Way to go, internet.
HowDoIVoIP said:
tony, I appreciate the guide but having never rooted or flashed a sony device, can I follow your guide to a T or do I sort of have to follow the main guide by Miustone as well as yours?
For example, he mentions installing "Fastboot" and "Flashmode" drivers by rebooting Windows 10 and installing them with Driver Signature Enforcement disabled. You didn't mention this, so I'm just trying to determine if I need to sort of follow both guides.
Click to expand...
Click to collapse
tonysunshine said:
so I had to jump through a few threads to figure out the details on how to update a magisk rooted x1m3 to the latest firmware without wiping(dirty flash). Figured I'd write out the steps here for others benefits
1 - download the firmware with Xperifirm
2 - download newflasher and extract to the firmware folder
3 - delete the following files from the firmware folder for no wipe dirty flash - userdata.sin, appslog.sin, diag.sin and metadata.sin. Skip this step if you're using Newflasher v52 and above
4 - download UnSin and extract to the firmware folder
5 - in the firmware folder, drag and drop boot_X-FLASH-ALL-*.sin into unsin.exe, and it will generate a boot_X-FLASH-ALL*.img in the same folder
6 - copy the boot_X-FLASH-ALL*.img onto your phone's sdcard somewhere.
7 - using magisk manager, install magisk and use the "select and patch a file" method. Select the boot_X-FLASH-All*.img file. This will generate a magisk_patched*.img onto your phone's sdcard
8 - download and extract platform-tools. Copy the magisk_patched*.img file from your phone's sdcard into the platform-tools folder on the computer. Rename the file to simply "magisk_patched.img"
9 - back up the phone
10 - shut down the phone, plug in a usb-c cable to the computer, then while holding the volume DOWN button, plug in the usb-c cable to the phone. The LED indicator should be GREEN indicating FLASHMODE
11 - open up cmd prompt, and navigate to the firmware folder from step 1. Type in the following command
Code:
newflasher set_active:a
then hit enter. You should see result like this
View attachment 5423107
12 - in windows explorer, navigate to the firmware folder, and double click on newflasher.exe(phone should still be in FLASHMODE). Respond to the prompts - n gordongate, p power off, n trim
13 - wait for the flashing of the new firmware to finish
14 - disconnect the phone from the usb cable, and power it back up. Check and make sure you have all your data/apps/etc. At this point it should boot into the rom just fine, but won't have root access and magisk will show that its not installed
15 - power off the phone again. This time, press the volume UP button while plugging in the USB-C cable. LED indicator should be BLUE for FASTBOOT
16 - open up a new cmd prompt, navigate to the platform-tools folder. Type
Code:
fastboot devices
and hit enter to confirm your phone is connected. Should respond with an alphanumeric number and the term fastboot
17 - type the following commands into cmd prompt
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
18 - DONE. Your phone should be on the new firmware with root and all your data/apps/etc
props to @Miustone, @OhayouBaka, @Forbesii for the original instructions. I just sort of put it all in one place
fingers crossed a great dev will come along and give us TWRP soon!
Click to expand...
Click to collapse
tony, I appreciate the guide but having never rooted or flashed a sony device, can I follow your guide to a T or do I sort of have to follow the main guide [email protected] Miustone as well as yours?
For example, he mentions installing "Fastboot" and "Flashmode" drivers by rebooting Windows 10 and installing them with Driver Signature Enforcement disabled. You didn't mention this, so I'm just trying to determine if I need to sort of follow both guides.
HowDoIVoIP said:
tony, I appreciate the guide but having never rooted or flashed a sony device, can I follow your guide to a T or do I sort of have to follow the main guide [email protected] Miustone as well as yours?
For example, he mentions installing "Fastboot" and "Flashmode" drivers by rebooting Windows 10 and installing them with Driver Signature Enforcement disabled. You didn't mention this, so I'm just trying to determine if I need to sort of follow both guides.
Click to expand...
Click to collapse
Yeah you will want to follow @Miustone 's guide first. I wrote mine assuming the phone has already been bootloader unlocked and rooted and the PC is setup already
tonysunshine said:
Yeah you will want to follow @Miustone 's guide first. I wrote mine assuming the phone has already been bootloader unlocked and rooted and the PC is setup already
Click to expand...
Click to collapse
Well thanks anyway, dude. I just followed most of his tutorial through step 4 all the way to fastboot flash boot_b magisk_patched.img
and then I just followed you with fastboot reboot without doing fastboot -w to wipe it. Well, it was wiped anyway. I guess I don't know what I expected. Lost everything and it's still not ****ing rooted - at least according to Youtube Vanced.
Ugh. This blows. We need better instructions. What was the point of flashing exactly when all it did was ERASE everything and not even grant you root?
Now I don't know what to do. I didn't even get to your "newflasher" here because I was following main guide and I stopped at the end of step 4 like like others said. I only wanted root. I didn't want to flash a new ROM.
Edit: Re-installed Magisk and now I can grant superuser. I still think these instructions need to be clearer for those of us who haven't rooted anything in thousands of years.
Unfortunately when you unlock your bootloader it will wipe the phone no matter what.
Will the tutorial in the first post also work on the Xperia Ace 3?
tonysunshine said:
so I had to jump through a few threads to figure out the details on how to update a magisk rooted x1m3 to the latest firmware without wiping(dirty flash). Figured I'd write out the steps here for others benefits
1 - download the firmware with Xperifirm
2 - download newflasher and extract to the firmware folder
3 - delete the following files from the firmware folder for no wipe dirty flash - userdata.sin, appslog.sin, diag.sin and metadata.sin. Skip this step if you're using Newflasher v52 and above
4 - download UnSin and extract to the firmware folder
5 - in the firmware folder, drag and drop boot_X-FLASH-ALL-*.sin into unsin.exe, and it will generate a boot_X-FLASH-ALL*.img in the same folder
6 - copy the boot_X-FLASH-ALL*.img onto your phone's sdcard somewhere.
7 - using magisk manager, install magisk and use the "select and patch a file" method. Select the boot_X-FLASH-All*.img file. This will generate a magisk_patched*.img onto your phone's sdcard
8 - download and extract platform-tools. Copy the magisk_patched*.img file from your phone's sdcard into the platform-tools folder on the computer. Rename the file to simply "magisk_patched.img"
9 - back up the phone(since still no real TWRP and titanium backup has been broken for a long time, I've been using Swift Backup)
10 - shut down the phone, plug in a usb-c cable to the computer, then while holding the volume DOWN button, plug in the usb-c cable to the phone. The LED indicator should be GREEN indicating FLASHMODE
11 - open up cmd prompt, and navigate to the firmware folder from step 1. Type in the following command
Code:
newflasher set_active:a
then hit enter. You should see result like this
View attachment 5423107
12 - in windows explorer, navigate to the firmware folder, and double click on newflasher.exe(phone should still be in FLASHMODE). Respond to the prompts - n gordongate, p power off, n trim
13 - wait for the flashing of the new firmware to finish
14 - disconnect the phone from the usb cable, and power it back up. Check and make sure you have all your data/apps/etc. At this point it should boot into the rom just fine, but won't have root access and magisk will show that its not installed
15 - power off the phone again. This time, press the volume UP button while plugging in the USB-C cable. LED indicator should be BLUE for FASTBOOT
16 - open up a new cmd prompt, navigate to the platform-tools folder. Type
Code:
fastboot devices
and hit enter to confirm your phone is connected. Should respond with an alphanumeric number and the term fastboot
17 - type the following commands into cmd prompt
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
18 - DONE. Your phone should be on the new firmware with root and all your data/apps/etc
props to @Miustone, @OhayouBaka, @Forbesii for the original instructions. I just sort of put it all in one place
fingers crossed a great dev will come along and give us TWRP soon!
Click to expand...
Click to collapse
What about deleting all the .ta files? I think this is a precautionary step so that the bootloader is not messed with in the case that you install an older firmware. My understanding is that if the bootloader is downgraded with those .ta files from older firmware, this will cause a brick.