Database Info

[HOWTO] Acquire root on a German/European Milestone (v2.1.31/34)

Welcome
I am 2 lazy to translate so I just write my own and personal tested HOW-TO for getting root on a German 2.1 Milestone. This should also work with any European version of the Motorola Milestone (not tested!!!)
I take no responsibility for any damages done to your device.
You will void your warranty with rooting your phone!
File and idea sources: http://www.android-hilfe.de/root-ha...1-update-mit-oder-ohne-root-fuer-dummies.html
Required:
BRAIN!
Milestone with Firmware 2.1
Motorola USB Drivers
RSD Lite
Vulnerable Recovery SBF
Sera’s update.zip
Step 1
BACKUP YOUR F.. DEVICE
Dont need to explain that. Keyword: Nandroid
Step 2
Start your device in Bootloader Mode
You do that by pressing D-Pad up (hold it in landscape mode) and while holding this key start it up with power button. The bootloader screen should show up after some seconds.
Step 3
Connect your Milestone to your Computer via USB and be sure your device is recognized correctly!!!
Now start RSD lite, select the Vulnerable Recovery SBF File and hit the start button.
If the button is greyed out try to rename the sbf file so sth. shorter.
If you get an error on this you have to try by commandline:
First of all you should rename the SBF file to something simple like „recovery.sbf“ and copy it to C:\.
Navigate to your RSD directory using the „cd“ command.
Now type f.e. „SDL.exe -f c:\recovery.sbf -t 2“.
RSD should popup and do the job for you
Step 4
After the flashing progress your device is starting up and now everything you have to do is to root your phone. Thats very simple and working with the provided update.zip. Copy this file to the root of your SD-Card.
Now start up the phone in recovery mode with holding your camera button pressed while pressing the power button. The M-Logo shows up after around 5 seconds and after some further seconds there should be a /!\ sign.
Release the keys as soon you see this. Now hold your VOL-UP button pressed while hitting the camera button again.
You should now be in the recovery console. – FINALLY – select the update.zip with the hardware-keypad. This should only take some seconds till ist complete.
Reboot and everything is fine now
Undo root
Use ADB-Shell to run following commands
Code:
mount system
rm /system/bin/su
rm /system/app/Superuser.apk
umount system
Correct me if I forgot sth.

great. i'll give it a try.
many thanks.

Sorry to jump here late.
I'm trying to root my Milestone. Bought this as NAM unlocked phone from Negri but it's clearly stamped as Made in Brazil A853 Model.
tested Step 2 and does:
Code:
Bootloader 90.78
Battery OK
OK to Program
Connect USB
Data Cable
I have the 2.1-update1 firmware.
Any ideas if this will work on my phone?
I been digging around the whole internet and it gets confusing either this will work right or not. Mainly because of the issue regarding the bootloader on the previous 2.0 versions and signed bootloader.
Also I run Ubuntu on my PC although I have a windows7 lap from my wife, but would like to do it under linux. Possible?
(I wonder WHY Motorola manufacture a Linux phone with solely windows drivers?)
Any help appreciated.

milestone
Hi guys, i flashed 2.2 into my milestone. At first, it worked fine but recently, the screen has going bonkers. Like sometimes the icons are being pressed without me pressing and sometimes i cannot unlock my phone. How is this possible?

[Q] How bad did I brick my Kyros 7005??

Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe

can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.

I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.

do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.

Solution: Gtablet can not power on or reboot after nvflash

I hope my post will help somewhat those buddies who had the same problem or who will probably have this problem in future.
I had the problem that my gtablet couldn't power on after I did Nvflash. I'd been frustrated in the past week for searching the internet to find the way out.
The similar problem that tcrews had. (http://forum.xda-developers.com/showthread.php?t=903684)
Also some posts I browsed:
http://forum.xda-developers.com/showthread.php?t=999287
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
http://forum.xda-developers.com/showthread.php?t=927006
http://forum.xda-developers.com/showthread.php?t=971608
http://forum.xda-developers.com/showthread.php?t=938706
I am grateful to tcrews and a lot of other buddies for their inputs which saved me lots of time, though i didn't find a right solution from their posts. Acidburn89's solution in tcrews's post (page 9) didn't work out for me either.I don't know whether tcrews solved his problem in acidburn89's method.
I tried all the methods I could find and nothing worked out for me. The only way I can turn the tablet on is to follow tcrews's post on rebooting the tablet by using nvflash (nvflash --bl bootloader.bin --download 9 recovery.img --go)
Some background of bricking my gtablet:
1.my gtab had CWM0.8.and was running rom "zpad clean 3.0" (before that it was TNTL, not any problem)
2.one week ago, I was trying to flash a rom from a chinese website, which was modified from the official malata zpad rom. This was the problem started from. After flashing (nvflash method),the tab was rebooting and stuck at "Tegra II" logo and couldn't never start with the new rom. At this moment, i could still power on and off the tab.
3.next I flashed my tab by following this link (http://forum.xda-developers.com/showthread.php?t=861950) After flashing it, the tab couldn't not reboot, and could not power on. Every time I pressed the power button, it just went to the APX mode authomatically
(with black screen).Only using the above-mentioned method (from tcrews) I could start the tab.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/showpost.php?p=9837354&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
2.Copy recovery-stock.img into the nvflash folder.
3.Start the tab by nvflash (tcrews' method)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
I tried this method with and without CWM. Both worked. So don't worry whether you tab has CWM or original recovery. My advice: flash your favorite rom using sdcard method instead of nvflash. If you want to nvflash it, save all the files we have used for possilbe repeation of our above job to get your tab back to life!!
I've received a lot of information and help from xda-development before, and hope my first post could contribute to our community a little bit.

Just noticed that idocinthebox has the same idea of correcting recovery.img in this post:
http://forum.xda-developers.com/showthread.php?t=994046

Master
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)

Well done! If this helps anybody mash the thanks button ;-) ^^^^^^^^^^^

Exact same issue
Can you provide your stock update.zip file? I have not been able to find a file that works for me. So far I have repeated this process many times with many update.zip fules but its still wont start on its own.

I can fin a update.zip.... can you posted here?
Thanks.

I follow this thread but still my gtab is power on APX (only). I was using the stock 3588 and went to the new 4349... start to having issues decided to go back to 3588 using the nvflash. it worked at the first time (until I had the tablet on) As you turned of and turned on, just a black screen (apx) and the only way to get it back is running the nvflash again but if I turned off have to do it again.
Please help!!!!
I can't figure it out on my own.

The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/show...54&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
*** could you posted your original (stock rom) update.zip? The one above mention is not in zip format. I did a zip format but still not working.
2.Copy recovery-stock.img into the nvflash folder. (i did that)
3.Start the tab by nvflash (I did that)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
*** the only way I could put the update.zip in the internal sdcard on the tablet was after nvflash the tablet power up, then I plug a usb drive (with update.zip in it) and copy to the internal sdcard... i did not plug the tablet to the computer.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
*** I did that the same way above mention from a usb drive.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
6,7,8,9,10,11 **** I did all but at the end still my tablet only work with nvflash unless I never turned off!!!

that download is corrupt...
Err it's the img ranamed... by bad..

Naysses and jettajon:
I uploaded the original update.zip I extracted from my G-tab. Try it to see whether it can help u.
w w w.mediafire.com/?fywhca6fi514toq
(remove space between "w"s)

I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly

Citi said:
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Click to expand...
Click to collapse
I ran across this post http://forum.xda-developers.com/showthread.php?t=1010659 which says that the BCT part of the nvflash isn't the same for all the GTablets and that's my experience.
I couldn't get nvflash_gtablet_2010110500.zip (from the dropbox repository of nvflash files) to work, but nvflash_gtablet_46_2010112600.zip worked fine.
The problem was that I couldn't get CM7 installed on my GTablet, but then I hacked the gtablet.cfg file to swap partitions 7 and 8 by merely cutting and pasting the partition 8 (name=OGO stuff) and putting it before the partition 7 (name=BLO stuff) to match the order of the gtablet.cfg in nvflash_gtablet_2010110500.zip.
Now CM7 has installed and seems to be working fine for me.
BTW- I didn't nvflash the CWM recovery since I was trying to minimize the number of things I was messing with. I assume it'll work, but I already had CWM installed on the internal emmc (SDCARD2) so really didn't even need to nvflash it.

Nope, I have tried both files and neither worked for me

kaluna00 said:
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Click to expand...
Click to collapse
guobug you are a hero
same thing happened to me
and because of you it works!!!
( followed the steps and used your updat.zip)
BUT I have another problem
when I tried to install CW
it says "Can't open sdcard/recovery.log"
now I dont know what to do
because I want to install another rom
I think there is something corrupted in the device after apx boot loop

You are a life saver. Worked like a charm. Have been reading through 50 million threads the last 3 days, and happened to find this one. Absolutely amazing. Thanks.

In step 8 I don't know where to type the code in, which Dos command, the dos command window which nvflash step opened( and I didn't press enter to close that window), or I have to open a new one( or make a new .bat file with the code).
I do it and cann't see it install the original rom( "You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashingtes" as you wrote in step 9)
So I still cann't fix my problem.
Please help me!

guobug said:
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
Click to expand...
Click to collapse
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.

BrandonJay21 said:
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
Click to expand...
Click to collapse
That error means the command 'nvflash' is not in the path for the windows command line.

Where do you type the DOS command at? Thanks.

when I hold the volume up and hit enter on the keyboard I get a bad command prompt. What am I doing wrong?

Rooting Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet

As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.

M7088
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
backslashx said:
As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.
Click to expand...
Click to collapse

Firmware
Hey awesome i may have a chance to try that method out on my tablet soon if i am lucky. I was wondering if anyone or the one that commented on my original post. I need a copy of the firmware for this tablet mine crashed after lending it out to a friend i am afraid he tried to modify it and somehow corrupted the system it is stuck on the dopo start up screen. if there is anyone who can provide a clean copy of this or even maybe dump a copy of theirs for me i would greatly appreciate it.
.
zxhwk said:
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
Click to expand...
Click to collapse

hey this is great news and I thank you !!!
I was wondering if the m7088 caan be upgraded to CM10/4.2.2?
thanks

I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.

Easy way to root any Dopo tablet
I am not responsible for anything. Use this at your on risk.
Download and install Exynos abuse .
Then Uninstall and get any kind of root checker to verify root access.
And that's it.
Worked for me with no problems. NOW My Dopo tablet is faster than when I got it out the box. With minor tweaking apps and my 32 gb external SD card as my internal SD card and you can find the thread on how to do this on xda forums. Running games like NFS MW, Modern Combat 2 and 3,Nba Jam for android.To run good games like these I had to get a system app freezer like titanium backup to freeze a few useless apps. So now these games run very smooth and flawlessly.Good luck.

backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
I ran across this post and was wondering if you have the original system and recovery images, as I rooted my M7088 and lost my backup files

m7088 firmware
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.

DOPO logo screen-freeze
putertim said:
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.
Click to expand...
Click to collapse
Joining just to make a couple comments here. I find that DOPO logo screen-freeze seems to be common problem.
My story - This passed Christmas 2012 my son purchased a DOPO M7088 for his 12y/o son, and talked me into a like purchase for myself this past March 2013. Here in Jul 2013, the grandson is visiting with his tablet. When it became frozen with the DOPO screen one night - we tried everything that we could think of to restore. Even pointing fingers at him... to what surprise the following morning my tablet froze updating apps. When I tried to restart, reboot, reset... even tried Vol+/PwrUP, Vol-/PwrUP... allowing the power in the battery to drain to a point that the screen would not light up or flash. Then recharging - nothing worked passed the DOPO screen-freeze.
For reference - I have worked in electronics/computers from the late 60s - so I’m not a rookie here.
Fortunately – I purchased insurance with Wal-Mart, their tech-line made same suggestions as I had done to restore the system, and came to the conclusion that they will completely return/refund my purchase.
Strange that within 12hrs two like tablets crash following app updates, where one is for a young man (games) and the other for adult (general usage). The finger pointing had three other fingers pointing back at us. So apologies to the grandson.
My son may root/re-install the grandson’s system when they return home – for myself I’m going to upgrade to a better brand (now that I'm missing the tablet).
Hope this helps others to understand that the DOPO screen-freeze problem may not be their personal tablet problem but a product problem (I.E. firmware). /TDos

Need dump of 7088 rom
backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
Hello, I have damaged the ROM by a an installed app after rooting. I see you said that you made a dump of the ROM. If possible, can I get a copy of these files as this would help me greatly. I have rkAndroidTool.exe working. If it works out, I will post the procedure.
Thanks

Dump and Flash the dopo M7088 and other RK3066 based ROMs
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link http://www.ubuntu.com/download/desktop .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link: http://download.cnet.com/ImgBurn/3000-2646_4-10847481.html?tag=mncol;2
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link: https://docs.google.com/file/d/0B8YnQA1FX-_yUU1ERXh1TjNUbnc/edit?usp=sharing

Thanks
I now have my M7088 again. Thank you . Your instructions where 100% right on.

Partition table not correct in stock M7088 ROM!
After I created the dump of the M7088 ROM and I flashed my tablet, I was looking at the parameter file and realized it was wrong from the factory!
There are several problems that may be the reason some people (including me) has had their devices brick for no apparent reason.
Below is the factory partition table. There is a blank space at address 118000 for a length of 11E000 bytes, this is not a problem. However, the "userdata" partition overruns the "kpanic" and "system" partition as well as the "system" partition overruns the "user" partition. This could lead to data corruption in the partitions.
Factory Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
(ERROR - Space between 118000 and 236000)
[email protected](userdata), (236000 + 400000 = 636000)
(ERROR - 636000 is past 618000 and 61A000)
0x000020[email protected](kpanic), (618000 + 2000 = 61A000)
[email protected](system), (61A000 + 200000 = 81A000)
(ERROR - 81A000 is past 73A000)
[email protected](user) (73A000 -> end)
It looks like someone made a mistake and/or adjusted the partition sizes and never finished the job!
The only way to fix this is to correct the partition table and re-flash the entire device.
Before I corrected the "parameter" and "parm.img" file, I examined other RK3066 roms as well as the dopo TD1010. The TD1010 has a shorter "system" partition so the fixed partition table below is the same as the TD1010 all the way through the "kpanic" partition.
Fixed Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
[email protected](userdata), (118000 + 400000 = 518000)
[email protected](kpanic), (518000 + 2000 = 51A000)
[email protected](system), (51A000 + 200000 = 71A000)
[email protected](user) (71A000 -> end)
I corrected the stock firmware and repacked it as dopo7088stkfixed.zip. This file can be flashed with the procedure in the earlier post, replacing the original zip package with this one.
Fixed Firmware Link: https://docs.google.com/file/d/0B8YnQA1FX-_yRmhIN1dCT245R2c/edit?usp=sharing
Also, remember to do a full wipe after flashing.
Thanks
---------- Post added at 02:12 PM ---------- Previous post was at 01:51 PM ----------
putertim said:
I now have my M7088 again. Thank you . Your instructions where 100% right on.
Click to expand...
Click to collapse
No problem. Check my above post. I discovered the partition tables from the factory are wrong which could cause data corruption.
Thanks

i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$

bird56duce said:
i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$
Click to expand...
Click to collapse
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
{
"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"
}

opening awsfai
mikeopi said:
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
Click to expand...
Click to collapse
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks

bird56duce said:
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks
Click to expand...
Click to collapse
Hold the power key for about 15 seconds to force a shut down.
After shutting down, do you still get a stuck dopo screen?
If so, try a different USB port on the PC and try the procedure again. Sometime it does not seem to always take.
Make sure you are using the command sudo ./flashall.sh with the fixed rom. For the fixed rom to work, you have to flash all partitions. Then do a factory reset once it is fully booted.
Also, do a wipe. With the power off, hold the vol- and power key. This should bring you into the recovery menu. Do a wipe cache & wipe data/factory reset & reboot.

I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.

mvalent000 said:
I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.
Click to expand...
Click to collapse
Please give me more info on what the errors are and what command are they after?

mikeopi said:
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link:
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link:
Click to expand...
Click to collapse
I have tried this today about 8 times today. 4 with each folder you supplied in every usb port on my computer. I could do it all the way down to the dumping. I couldn't get any of the flashing working and my m7088 tablet is still stuck on the dopo screen. Please help as I would like to have this tablet working for my way home in a week.
I have Linux as a second os on my laptop so the first part was easy.
Thanks for your help so far. Good info

Bricked Idol 3, need help recovering

I installed the OTA update last night and it's just looping through the "alcatel one touch" and "smart move" screens. It's been like that for hours.
I need assistance in getting into recovery mode, and hopefully getting my files off the device.
I have downloaded android-studio and am about to install it to get adb and fastboot, and have downloaded the drivers for the idol 3. At this point when it's plugged in, my computer doesn't recognize the device.

If you did not have usb debugging enabled BEFORE the boot loop installing adb and fastboot now won't do you any good. Are you still able to get into recovery and is it twrp or the factory recovery? Without a direct way to get the phone into bootloader regretfully the only solution is to send it in for warranty repair (or replacement via your credit card if you paid that way under purchase protection)
Are you trying to remove the data to prevent access by others or because you need the data? Did you make any backups to external sd or copied to the pc?

I as well am stuck in bootloop. Was able to get into factory recovery and reset phone several times. Still no luck. I have a TWRP backup, but how to I do a temporary boot into it? Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there. Phoned Alcatel and they have referred me back to Amazon. Amazon only wants to refund me, won't exchange! Of course I bought at the pre-order price. Any help would be greatly appreciated.

wrench588 said:
I as well am stuck in bootloop. Was able to get into factory recovery and reset phone several times. Still no luck. I have a TWRP backup, but how to I do a temporary boot into it? Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there. Phoned Alcatel and they have referred me back to Amazon. Amazon only wants to refund me, won't exchange! Of course I bought at the pre-order price. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The factory reset killed you....if you had usb debugging enabled prior and had not done a factory reset (which kills /data) you could have possibly gotten to an adb shell long enough to do an adb reboot bootloader. The problem is there's no way now to get you into bootloader....you can't get to it from recovery (factory).
If you purchased it by credit card you might see if their purchase protection (typically 60-90 days) allows a claim submission for a replacement....in this case they would cut you a check for the cost of a replacement after mailing in your old one. That's the only solution I see to remain at the $199 price.
You could also see if amazon will issue a $50 credit to your account in addition to return to allow for repurchase. Unlikely but possible.

Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.

wrench588 said:
Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.
Click to expand...
Click to collapse
Nothing so far has worked in that regard...in fact I created a update.zip using "zipme" to replace the build.prop that another user says the factory recovery refused to process.
Without a full factory rom to pull needed info in or the source code to compile one we can't do some of the things which would "save" the device.

wrench588 said:
...Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there.
Click to expand...
Click to collapse
Strange ... the stock recovery of 6039y has an option for reboot to the bootloader.

petrov.0 said:
Strange ... the stock recovery of 6039y has an option for reboot to the bootloader.
Click to expand...
Click to collapse
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.

famewolf said:
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.
Click to expand...
Click to collapse
There is no option for screenshot while the phone is in the stock recovery. I need a camera to take a picture of the menu. I can do this later. The menu however looks like this:
Code:
reboot system now
apply update from ADB
apply update from sdcard
apply update from phone storage
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery log

petrov.0 said:
There is no option for screenshot while the phone is in the stock recovery. I need a camera to take a picture of the menu. I can do this later. The menu however looks like this:
Code:
reboot system now
apply update from ADB
apply update from sdcard
apply update from phone storage
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery log
Click to expand...
Click to collapse
If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.

famewolf said:
If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
Click to expand...
Click to collapse
This is a snapshot from the recovery menu of 6039y.
The short answer of your question regarding the "lock" is ... no. If a longer explanation is needed ... this is from the update file, a link to which was provided by you:
Code:
if ! applypatch -c EMMC:/dev/block/bootdevice/by-name/recovery:18393344:f9062580503eb61b315a5d12c5c6b3bb133aa4b2; then
....etc.
what it does is to check the sha1 sum of the recovery partition and if the sha1 sum doesn't match to f9062580503eb61b315a5d12c5c6b3bb133aa4b2 will continue with an overwriting of the recovery partition and then will apply a patch. It can't be changed because the whole update will fail.

yep no bootloader

I've got reboot to boatloader on main page from stock recovery on my 6045k
Sent from hell

famewolf said:
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
Click to expand...
Click to collapse
Back to the "lock" question. Probably it is possible the OTA update to be slightly modified and then to be flashed through the TWRP recovery (there is an option in TWRP to skip the signature verification ... the verification will fail if the zip file is modified). But I prefer to wait for the OTA update of the 6039y, as I want to perform some tests with the upgrade.

ractar28 said:
I installed the OTA update last night and it's just looping through the "alcatel one touch" and "smart move" screens. It's been like that for hours.
I need assistance in getting into recovery mode, and hopefully getting my files off the device.
I have downloaded android-studio and am about to install it to get adb and fastboot, and have downloaded the drivers for the idol 3. At this point when it's plugged in, my computer doesn't recognize the device.
Click to expand...
Click to collapse
I am in the same boat as OP re the state my Idol 3 (6045i) is currently in. I also unchecked superuser but did not unroot completely before installing the update. I have not yet done a data wipe through recovery though. Unfortunately, back when I rooted the phone I did NOT check the box telling the phone to remember the computer/RSA key for future use. As a result, now when the phone is stuck at the white/animated Alcatel boot logo I can see the phone under adb devices, but it shows as unauthorized.
One thing that did seem odd, was browsing through stock recovery when trying to browse to apply an update from either phone storage or the SD card, no files are showing up at all. All it is showing is the folder root ( /.. ) in both instances and nothing else. Even after I attempted loading several system update and twrp images (in .zip and .img formats) on the SD card from my computer, once loaded in the phone none of the files show up through stock recovery. Is this SD card not compatible/formatted wrong or is something else going on?
Is there any current method to gaining access to the phone via adb manupulating the adbkey files in the $User$/Home/.android folder? I do currently have the adbkey files on my Mac from connecting the phone previously. I'm assuming these files are uniquely generated hashes?
That is ridiculous if the 6045k has bootloader access from recovery and 6045i does not. What would be the reasoning for this?

Nikola Jovanovic said:
I've got reboot to boatloader on main page from stock recovery on my 6045k
Sent from hell
Click to expand...
Click to collapse
Does the sha1 sum of your recovery happen to match f9062580503eb61b315a5d12c5c6b3bb133aa4b2 ? If so it could solve some issues but why do I suddenly think all 3 models have their own recovery?
---------- Post added at 08:47 AM ---------- Previous post was at 08:43 AM ----------
n3tnut said:
I am in the same boat as OP re the state my Idol 3 (6045i) is currently in. I also unchecked superuser but did not unroot completely before installing the update. I have not yet done a data wipe through recovery though. Unfortunately, back when I rooted the phone I did NOT check the box telling the phone to remember the computer/RSA key for future use. As a result, now when the phone is stuck at the white/animated Alcatel boot logo I can see the phone under adb devices, but it shows as unauthorized.
One thing that did seem odd, was browsing through stock recovery when trying to browse to apply an update from either phone storage or the SD card, no files are showing up at all. All it is showing is the folder root ( /.. ) in both instances and nothing else. Even after I attempted loading several system update and twrp images (in .zip and .img formats) on the SD card from my computer, once loaded in the phone none of the files show up through stock recovery. Is this SD card not compatible/formatted wrong or is something else going on?
Is there any current method to gaining access to the phone via adb manupulating the adbkey files in the $User$/Home/.android folder? I do currently have the adbkey files on my Mac from connecting the phone previously. I'm assuming these files are uniquely generated hashes?
That is ridiculous if the 6045k has bootloader access from recovery and 6045i does not. What would be the reasoning for this?
Click to expand...
Click to collapse
adb reboot bootloader won't work even with it showing unauthorized? If you can get into bootloader you can fix /system without messing up your /data (don't wipe data or you lose adb entirely...you may figure out how to add the correct hash if we can find how it's generated)
Here's some info on the hashes you might find useful taken from: http://nelenkov.blogspot.com/2013/02/secure-usb-debugging-in-android-422.html
Secure ADB implementation
The ADB host authentication functionality is enabled by default when the ro.adb.secure system property is set to 1, and there is no way to disable it via the system settings interface (which is a good thing). The device is initially in the OFFLINE state and only goes into the ONLINE state once the host has authenticated. As you may already know, hosts use RSA keys in order to authenticate to the ADB daemon on the device. Authentication is typically a three step process:
After a host tries to connect, the device sends and AUTH message of type TOKEN that includes a 20 byte random value (read from /dev/urandom).
The host responds with a SIGNATURE packet that includes a SHA1withRSA signature of the random token with one of its private keys.
The device tries to verify the received signature, and if signature verification succeeds, it responds with a CONNECT message and goes into the ONLINE state. If verification fails, either because the signature value doesn't match or because there is no corresponding public key to verify with, the device sends another AUTH TOKEN with a new random value, so that the host can try authenticating again (slowing down if the number of failures goes over a certain threshold).
Signature verification typically fails the first time you connect the device to a new host because it doesn't yet have the host key. In that case the host sends its public key in an AUTH RSAPUBLICKEY message. The device takes the MD5 hash of that key and displays it in the 'Allow USB debugging' confirmation dialog. Since adbd is a native daemon, the key needs to be passed to the main Android OS. This is accomplished by simply writing the key to a local socket (aptly named, 'adbd'). When you enable ADB debugging from the developer settings screen, a thread that listens to the 'adbd' socket is started. When it receives a message starting with "PK" it treats it as a public key, parses it, calculates the MD5 hash and displays the confirmation dialog (an activity actually, part of the SystemUI package). If you tap 'OK', it sends a simple simple "OK" response and adbd uses the key to verify the authentication message (otherwise it just stays offline). In case you check the 'Always allow from this computer' checkbox, the public key is written to disk and automatically used for signature verification the next time you connect to the same host. The allow/deny debugging functionality, along with starting/stopping the adbd daemon, is exposed as public methods of the UsbDeviceManager system service.
We've described the ADB authentication protocol in some detail, but haven't said much about the actual keys used in the process. Those are 2048-bit RSA keys and are generated by the local ADB server. They are typically stored in $HOME/.android as adbkey and adbkey.pub. On Windows that usually translates to %USERPOFILE%\.android, but keys might end up in C:\Windows\System32\config\systemprofile\.android in some cases (see issue 49465). The default key directory can be overridden by setting the ANDROID_SDK_HOME environment variable. If the ADB_VENDOR_KEYS environment variable is set, the directory it points to is also searched for keys. If no keys are found in any of the above locations, a new key pair is generated and saved. On the device, keys are stored in the /data/misc/adb/adb_keys file, and new authorized keys are appended to the same file as you accept them. Read-only 'vendor keys' are stored in the /adb_keys file, but it doesn't seem to exist on current Nexus devices. The private key is in standard OpenSSL PEM format, while the public one consists of the Base 64 encoded key followed by a `[email protected]` user identifier, separated by space. The user identifier doesn't seem to be used at the moment and is only meaningful on Unix-based OS'es, on Windows it is always '[email protected]'.
While the USB debugging confirmation dialog helpfully displays a key fingerprint to let you verify you are connected to the expected host, the adb client doesn't have a handy command to print the fingerprint of the host key. You might think that there is little room for confusion: after all there is only one cable plugged to a single machine, but if you are running a couple of VMs, thing can get a little fuzzy. Here's one of way of displaying the host key's fingerprint in the same format the confirmation dialog uses (run in $HOME/.android or specify the full path to the public key file):
awk '{print $1}' < adbkey.pub|openssl base64 -A -d -a \
|openssl md5 -c|awk '{print $2}'|tr '[:lower:]' '[:upper:]'
We've reviewed how secure ADB debugging is implemented and have shown why it is needed, but just to show that all of this solves a real problem, we'll finish off with a screenshot of what a failed ADB attack against an 4.2.2 device from another Android device looks like:

famewolf said:
adb reboot bootloader won't work even with it showing unauthorized? If you can get into bootloader you can fix /system without messing up your /data (don't wipe data or you lose adb entirely...you may figure out how to add the correct hash if we can find how it's generated)
Click to expand...
Click to collapse
Just tested using adb reboot bootloader again and this is the result: error: device unauthorized. Please check the confirmation dialog on your device.
Something else I tried was running fastboot commands in the narrow window that the phone initially boots (black screen with Android logo) but that didn't seem to work either. I tried:
fastboot reboot-bootloader
fastboot -i 0x1bbb reboot-bootloader
fastboot -i 0x1bbb devices
I noticed if you plug the phone into the computer via USB while the phone is off, it will briefly power on to the Android logo/black screen before flashing the battery status once and turning off. Is this an opportunity to send fastboot or adb commands to the phone?
I'll try messing with the adbkey stuff later when I have time to dig into it.

There is a tool from Alcatel (TCL) which can perform upgrades of the device from a Windows PC. You can try it if nothing else helps. There are two COM ports available under Windows when the device is powered off and the USB cable is connected to the phone. This tool use them to perform some checks on the device and probably will continue with an upgrade (it says that all of your data will be wiped after the upgrade etc. so there is a possibility to overwrite everything with a stock image) ... there are instructions how to work with it. The link is from the French support section of Alcatel. Despite that the program has support for 6039 and 6045 is not clear for which of their versions.

petrov.0 said:
There is a tool from Alcatel (TCL) which can perform upgrades of the device from a Windows PC. You can try it if nothing else helps. There are two COM ports available under Windows when the device is powered off and the USB cable is connected to the phone. This tool use them to perform some checks on the device and probably will continue with an upgrade (it says that all of your data will be wiped after the upgrade etc. so there is a possibility to overwrite everything with a stock image) ... there are instructions how to work with it. The link is from the French support section of Alcatel. Despite that the program has support for 6039 and 6045 is not clear for which of their versions.
Click to expand...
Click to collapse
The problem is we currently have no stock images in the format it requires to flash to restore the device. I would think those have to be available first?
---------- Post added at 02:56 AM ---------- Previous post was at 02:55 AM ----------
n3tnut said:
Just tested using adb reboot bootloader again and this is the result: error: device unauthorized. Please check the confirmation dialog on your device.
Something else I tried was running fastboot commands in the narrow window that the phone initially boots (black screen with Android logo) but that didn't seem to work either. I tried:
fastboot reboot-bootloader
fastboot -i 0x1bbb reboot-bootloader
fastboot -i 0x1bbb devices
I noticed if you plug the phone into the computer via USB while the phone is off, it will briefly power on to the Android logo/black screen before flashing the battery status once and turning off. Is this an opportunity to send fastboot or adb commands to the phone?
I'll try messing with the adbkey stuff later when I have time to dig into it.
Click to expand...
Click to collapse
You can't do fastboot commands until the phone is IN bootloader....so you'd have to do adb reboot bootloader
adb devices
etc....

famewolf said:
The problem is we currently have no stock images in the format it requires to flash to restore the device. I would think those have to be available first?
Click to expand...
Click to collapse
It is possible the program to download these images from a server.
I found another interesting thing. The device has a download mode. It is activated when the phone is powered off and connected to a PC. You must wait the display to turn off after the charging battery symbol and then to press and hold both volume keys, after which to press and hold the power button (without releasing these for the volume). But still don't know what to do in this mode. No device is detected on my Linux box when the phone is in this state. Probably I should try in Windows.
Also when the Alcatel upgrade tool was trying to detect the phone I'm almost sure that one of the COM ports was
Qualcomm HS-USB Diagnostics 9006
there is a lot information for other devices how this can be used to unbrick your phone, so this is a some start. The images which the people flash through it are in raw format.