Related
After seeing lots of different guides and struggling to understand them I have compiled a concise and easy to follow guide on fastboot, root, recovery, roms and ADB including lots of download links.
The idea is to stop people having to search high and low for a guide on how to do something and to provide easy to follow guides with no assumptions. Sort of like a central resource. This could be downloaded to your device and then all the download links are available wherever you are.
Most of it is my own work with inspiration taken from XDA and Modaco. Both forums have done a lot to help me so I thought it was time I gave back.
If you have any comments, corrections or suggestions then please email me at the email address in the attached document.
EDIT: Added lots of pictures and screen prints and converted to PDF only.
Thanks
Rob
i stickied, but havent read the documents.. but im sure its good useful information!
Im reading the pdf now looks good so far.
This should help alot of new and old users lol.
THANKS!!
change the title of the thread tho, looks too much like a rant from it along. something like "complete guide to everything" /shrug
Interesting! Thanks.
nice work thanks
Rob,
Thank you very much,
flumps said:
change the title of the thread tho, looks too much like a rant from it along. something like "complete guide to everything" /shrug
Click to expand...
Click to collapse
Good idea, done thanks!
One thing though, I appear to be missing a clockworkmod recovery? There are 4 on the guide (one from Koush's recovery and 3 from the clockworkmod guide sticky(2 on first page and 1 on page 3)). Is there another version somewhere or is it just those 4?
Thanks
Rob
shogunmark said:
i stickied, but havent read the documents.. but im sure its good useful information!
Click to expand...
Click to collapse
Thanks!
I've added lots of pictures and screen prints, sorted out the hyperlinks and converted to PDF only for compatibility.
Sounds Good I plan to download now
Hi, thanks for the guide but am stuck on one part. I want to basically install a custom recovery and am on Android 2.1.
The guide says to browse the Streaks folder via fastboot in a command prompt window, but how do you do that?
C and D drives are to do with the pc partitions but their are no others popping up when in Fastboot mode so am a little confused their.
"Navigate to your C:\streak folder by typing cd C:\streak and hitting Enter....."
I think he means use the command prompt to browse the folder that you downloaded and have named "Streak" so on the cmd, type "cd C:\streak" then enter and it should take you to the streak folder on your C drive which should have all the fastboot tools etc, at which point you can run the fastboot command. Am I right?
Thanks!
I would like to thank you Radddogg for this guide dude!
I'm new to Android and I got the gist of things by reading most of the threads on the Dell streak, but never truely understood what exactly was needed to flash ROM's, recovery's etc until I read your guide and it has made pretty much everything clear now....though I do still have a couple of questions
Firstly, just to clear things up in my mind, I know we use fastboot commands to install recovery images, but can we also use these commands to install actual ROM updates? If so, what is the difference between updating via the fastboot tool and via the recovery mode?
Secondly, I take it that we use stock recovery's for official ROM's and custom recovery's for custom ROM's, the question is, are there specific custom recovery's for specific custom ROM's or will any custom recovery work with any custom made ROM?
And lastly, which is required for leaked ROM's? Stock Recovery?
Thanks again Radddogg and thanks to anyone else who can help make me understand.
I understand now, will try it out tonight, cheers.
There won't be matching custom recovery/rom's. Just install the clockwork one and it will work fine.
hi Radddogg, thanks for your efforts.. but i went thru your pdf file, and tried so many times, just couldn't get yours to work.. i must have removed/replaced my battery like 50 times.. but i finally got mine to work.
i'm on 1.6 build 3883.. i kept getting the E:Can't find MISC error or blank screen trying the clock recovery 1.8.1.7, or your stock recovery.
Finally, what i did was:
1. load the 3883 superboot
loadbalancing.modaco.com/download.php?url=paul/streak/r1-3883-streak-superboot.zip
2. load the 4399 recovery
loadbalancing.modaco.com/download.php?url=paul/streak/r1-4399-streak-recovery.zip
3. load the 4399 pkg
loadbalancing.modaco.com/download.php?url=paul/streak/Streak_104_4399_21.pkg
4. and finally load the 8105 pkg using the 4399 recovery
info is here.
android.modaco.com/content/dell-streak-streak-modaco-com/310618/19-aug-streak-1-6-downloads-how-tos-rom-superboot-recovery/
Hi,
I'm not sure what you were trying to do as you didn't say but one thing I've found is that updates and recoveries are very build dependant and have to be done in order of build number. I'm not sure why you couldn't do what you wanted off the pdf as the downloads you posted are all available off my pdf?
The streak is definitely less user friendly than HTCs
Oh and is there a copy of the 3883 pkg anywhere I can add to the pdf?
sorry, i don't have a 3883 copy.
What was different was the sequence that i did it, and the versions to use.
Going thru your pdf, i followed point by point starting from point 1.. and i'm supposed to, after starting fastboot.. to do this
fastboot flash recovery recovery.img
But i get the blank screen. Not sure why, but i guessing i had to use this
fastboot –i 0x413c
for the recovery.img so i tried this but still not working. Maybe the recovery.img is not 4399 version.. and because i was on 3883, i had to use 4399?
When i tried
fastboot –i 0x413c flash recovery recovery-clockwork-streak.img
It worked, but then i get the "E:Can't find MISC" error. I'm guessing my pkg was the 8105 instead of the 4399. So tried loading 4399 pkg but same error. The clockwork thing didn't work for me.
Anyway, after trial and error many times, long story short, i downloaded the 4399 recovery and did this
fastboot –i 0x413c flash recovery recovery4399.img
load the 4399 pkg
load the 8105 pkg
and it finally worked. Would've helped if you had mentioned what version to use or that i had to load the 2 different versions of the pkg in sequence or maybe its just me. I didn't know.. i'm an android newbie..
But thanks anyway.
Hey sory if disturbing.
Below are my Streak details
Firmware 1.6
BaseBand GAUSB1AXXXXX00-EU
Kernel 2.6.29-perf
Build 6267
Please help me and let me know whic version will work
Super Boot ???
Clockworkmod ???
ROM ??
etc. etc. If some body already updated the same build into 2.1 please help me and give the instruction step by step.
Thanks
Hey!
Coming from an HD2, flashing ROMs shouldn´t be that difficult...but sadly it seems to be referring to the StreakDroid
I do know that flashing always comes with difficulties and has to be done with care...but I would be very thankful if anybody could help me out here and sum up the main steps, so I can get StreakDroid on my Streak too! I´ve read the whole thread (fards one), but I think it would be so much easier if anybody could take the time making a short tutorial how to flash the rom. It seems like the main bugs had overcomed...
Is there anybody out there who would do this for me and (I´m sure there are some/many) all the other guys who do not have the guts to start a try and error session? Would be soooo kind!!!!
greenlant said:
Hey!
Coming from an HD2, flashing ROMs shouldn´t be that difficult...but sadly it seems to be referring to the StreakDroid
I do know that flashing always comes with difficulties and has to be done with care...but I would be very thankful if anybody could help me out here and sum up the main steps, so I can get StreakDroid on my Streak too! I´ve read the whole thread (fards one), but I think it would be so much easier if anybody could take the time making a short tutorial how to flash the rom. It seems like the main bugs had overcomed...
Is there anybody out there who would do this for me and (I´m sure there are some/many) all the other guys who do not have the guts to start a try and error session? Would be soooo kind!!!!
Click to expand...
Click to collapse
Really.... did you not read any of the development threads at all with HUNDREDS of links to the flashing guides... and no its not ANYMORE complicated than than any other Android device once you get the correct drivers installed on your computer
greenlant said:
Hey!
Coming from an HD2, flashing ROMs shouldn´t be that difficult...but sadly it seems to be referring to the StreakDroid
I do know that flashing always comes with difficulties and has to be done with care...but I would be very thankful if anybody could help me out here and sum up the main steps, so I can get StreakDroid on my Streak too! I´ve read the whole thread (fards one), but I think it would be so much easier if anybody could take the time making a short tutorial how to flash the rom. It seems like the main bugs had overcomed...
Is there anybody out there who would do this for me and (I´m sure there are some/many) all the other guys who do not have the guts to start a try and error session? Would be soooo kind!!!!
Click to expand...
Click to collapse
Your gonna have to do some reading, it seems more complicated than it is.
I will give you hints, but no links.
Download and install Dell Streak drivers and PC Suite from Dell, look on the wiki here and find the fastboot drivers and exe and install those drivers.
Copy fastboot.exe to C:\ of your pc.
Next read about Streakmod and download the latest version, extract recovery.img and place it in c:\ on your pc.
Now flash recovery.img to the Streak using fastboot.
Now you can download StreakDroid 1.9.1, rename update.zip and place in the \ directory of your phones storage.
Now follow streakmod recovery procedure, turn on phone holding down volume up and down together, now you have a menu to do many things including update your phones firmware.
(InsertNameHere) said:
Your gonna have to do some reading, it seems more complicated than it is.
I will give you hints, but no links.
Download and install Dell Streak drivers and PC Suite from Dell, look on the wiki here and find the fastboot drivers and exe and install those drivers.
Copy fastboot.exe to C:\ of your pc.
Next read about Streakmod and download the latest version, extract recovery.img and place it in c:\ on your pc.
Now flash recovery.img to the Streak using fastboot.
Now you can download StreakDroid 1.9.1, rename update.zip and place in the \ directory of your phones storage.
Now follow streakmod recovery procedure, turn on phone holding down volume up and down together, now you have a menu to do many things including update your phones firmware.
Click to expand...
Click to collapse
well. here's the problem i faced. after spending whole day reading guides.. i am stuck on finding a recovery.img
my model is 357 and build number is 16864. it's not listed
sigh..
joule0930 said:
well. here's the problem i faced. after spending whole day reading guides.. i am stuck on finding a recovery.img
my model is 357 and build number is 16864. it's not listed
sigh..
Click to expand...
Click to collapse
You should contact TheManii. He is collecting/archiving all of the Streak builds he can find and as you write - I do not see BB 357 in the wiki.
Where did you get your phone? Did you buy it new or used? Is it locked to a carrier?
marvin02 said:
You should contact TheManii. He is collecting/archiving all of the Streak builds he can find and as you write - I do not see BB 357 in the wiki.
Where did you get your phone? Did you buy it new or used? Is it locked to a carrier?
Click to expand...
Click to collapse
I contacted him long ago but no reply. Maybe he is offline.
I bought my cell phone from India. we don't have carriers here.
it's a brand new phone and full unlocked with a price tag of 25k ( indian currency )
PM sent, keep in mind time zone differences. It was sent at 6am for me.
Bascially make a nandroid dump and send it to me
OP: Search for "MultiFlasher" thread, download files, read instructions and flash away. Even I got it done successfully. The fastboot driver is already included.
The main thing is you MUST have your phone's driver installed. This is the driver from Dell.
Sent from my Dell Streak using XDA App
Hello,
I wanna port CM to my Micromax A70...
Please tell me where to start and all that..
Any help is appreciated!
(Please don't post things like "It's impossible" etc etc if u don't wanna help )
If you need any info about this device please tell me!
pls read this thread very slowly and carefully. you should get a break through.
1. http://forum.xda-developers.com/showthread.php?t=667298
2. git.android.com / linux kernel.org has been hacked so you will not be getting a repo or a repo sync, if you go by current tutorials..
3. also it is better to go through dsixda's kitchen and see the innards of your rom before you jump into gingerbread.
4. I know that you are quite enthusiastic about porting cm7, but pls set up your adb properly.
lastly point number 1 is very important and point number 4 is most important.
also you did not reply whether the recovery key combination I told in techenclave booted you into recovery or not. pls let me know it then only we can proceed.
it is all a team work. so collaboration is an absolute requirement.
currently I am going through dsixda's kitchen.
seems playful god made the custom rom only from the above kitchen only..
All the best for early break through.
Sorry but it's really annoying at techenclave when it takes time for post to appear
I have already installed CWM recovery, hence I get CWM only..
I know cyanogen's thread and the kitchen..i'm into this since last 2 days...
but wtf is up with ADB, why isn't it working?
dont' know what issue with adb is. also we need to know how to get into download mode. it is something very similar to fastboot in htc. there is a utility called sut (software update utility) but we need adb first.
i'm using ubuntu 11.04. will try 10.10 for adb.
don't be angry if i tell you to be patient.
i've tried repo sync 7 times but failed. thats because i've limited bandwidth. bsnl plan 500 only free unlimited is 2am to 8am.
if we run into any bricking no body can help because
1. no adb
2. no download mode
cm7 might overwrite recovry partition so extreme caution is very essential.
any way we will do it. its just a matter of time. first let us get over the basics then it will all be fine
adityadeva said:
dont' know what issue with adb is. also we need to know how to get into download mode. it is something very similar to fastboot in htc. there is a utility called sut (software update utility) but we need adb first.
i'm using ubuntu 11.04. will try 10.10 for adb.
don't be angry if i tell you to be patient.
i've tried repo sync 7 times but failed. thats because i've limited bandwidth. bsnl plan 500 only free unlimited is 2am to 8am.
if we run into any bricking no body can help because
1. no adb
2. no download mode
cm7 might overwrite recovry partition so extreme caution is very essential.
any way we will do it. its just a matter of time. first let us get over the basics then it will all be fine
Click to expand...
Click to collapse
Hi Aditya,
I saw on androidforums that ADB is working on A70. You will have to install 91PC suite first. Will try soon and update you guyz.
hey guys i see you all are working very hard for making cm7 port for a70 but..... I jus wanted to know that which is the original manufacturer of micromax a70 i mean is it a rebrand of some other model .... Then we might be able to do something.... in some other thread i saw someone wrote that it is a rebrand if blade..
can u upload ur current rom
Can you guys dump ur current rom???
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
Hi,
I followed your instructions, but my God damned Windows 8.1 doesn't see my God damned Android 4.4.2, so I "adb devices" command -- pc doesn't see my Android. "file transfer (MTP) files" command is useless.
Is there any of you in the whole wide world could help me?
My phone is in recovery mode can't boot stuck in boot loop.
Nobody answeres. This is said to be the best geeks' forum.
Sorry, I am disappointed, fed up, etc. as none of you give a damn about my f***ing problem.
Thx if any...
You could try using the latest adb and some universal driver ***,
but not much use from ADB really, if it has a stock recovery Then also
making update zip s could be problematic... signing...
Best to try contacting the manufacturer or seller, what ever, and try to get the firmware + tools.
http://smartnavon.eu/
http://hungaroflotta.hu/page-7.html
http://hungaroflotta.hu/contact.html
If no luck, try to find out its soc. You could even try to open the damn thing...
Or just assume it's a MTK. If so -> MTK drivers, DroidTool, Wwr, SP_FlashTool, etc..
and make a backup. Worked ok? Good! Now find someone having the same piece of...
and ask her to do the same and share his system...
Good luck! :fingers-crossed::good:
*** For example this installer of mine. Contains universal adb driver and adb/fastboot downloader
https://forum.xda-developers.com/an...taller-universal-adb-driver-package-t3595277/
Thx 4 UR reply!
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Don't open it yet! :laugh: I did a bit more searching. It's a MT6572. This "dazexy" fellow
most likely can help if you cannot get that factory firmware.
http://forum.gsmhosting.com/vbb/f29...nfinity-box-725574-post10962286/#post10962286
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...rum.gsmhosting.com/vbb/10962286-post1173.html )
At least he helped "kaller1" at the same forum.... see the second post here.
(if needed you can find kaller1's email by clicking his paypal donate button)
http://forum.gsmhosting.com/vbb/f82...nck-dongle-1314877/index147.html#post11354667
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...d-phones-via-nck-dongle-1314877/index147.html )
Some more helpful people having d402??
https://mobilarena.hu/tema/navon_mizu_d402/hsz_1-50.html
So no worry, I think your problem will be solved. :highfive: (Hopefully...)
(if it is that Navon Mizu D402, as I assumed because of this post
https://forum.xda-developers.com/showthread.php?t=3501143 )
edit: gsmhosting works again. The second link (kaller1) updated to be more accurate.
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Here is another fellow who gives a damn. "donrico" is sharing the full rom here
http://forum.gsmkabelek.com/showthread.php?28404-navon-d402-rom&p=250246&viewfull=1#post250246
Because that 4shared site is a bit nasty, i copied it to mega, here
https://mega.nz/#!v4MgVIbJ!htsUcjHSrwwGIDuTeNRMAXKhxZOvVxJ8mnY3vMZoVks
Taking a full backup first might be a good idea.
SP_Flashtool should do the trick. You probably
can use the scatter file from that rom dump.
Or make your own: https://forum.hovatek.com/thread-21970.html
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Sub forum changed... Okay, let us continue here if needed.
Though you should be able to fix that damn thing now...
:victory:
Thank you so much for making such a hard effort to help me! ?
I'll do my best and will keep you informed.
Partitions "nvram" and in in my case also "pro_info" are important backups.
Nvram contains IMEI values etc... anyway it can be important to save it/them.
And pro_info might have some extra values defined in it. At least if the device
has some faked firmware showing wrong hardware values like in my case.
Then there might be some real values needed, defined there along with the faked ones...
I'm no MTK expert but managed to fix my tablet by restoring those partitions...
Ehh!
I've read all the info you linked. ????
OMG!
Well, I guess that I should download the rom.
After that do I have to do all the instructions?
How will my pc be able to see my phone?
I need no data backup.
I swear I got in touch with the store in which I bought the data cable and asked if it is really a data cable and not just a charging one.
I can do anything I just need to know the steps to be taken one by one.
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Nikkka said:
Ehh!
1. After that do I have to do all the instructions?
2. How will my pc be able to see my phone?
<snip>
3. There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Click to expand...
Click to collapse
1. I can relate your "shock". That Wwr route isn't the easiest one, I can imagine.
Haven't done it myself. Maybe that SP_FlashTool + scatter file is enough for
the backup. If you have those IMEI numbers saved you probably can skip
the backup, but as I said I'm no expert, so you might want to do some
Googling before deciding anything...
2. Install the MTK drivers (search). any tool will need them too.
3. IDK. Maybe someone else has an answer to this?
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Nikkka said:
Ehh!
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Click to expand...
Click to collapse
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
CXZa said:
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Click to expand...
Click to collapse
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
CXZa said:
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
Click to expand...
Click to collapse
Yep. Thanks.
Well, actually the antivirus Zemana asked if I wanted to make SELinuxModeChanger a part of the system/a system file. I agreed. I made the wrong decision. I used ES File Manager to delete SELinuxModeChanger. Well, I succeeded in half... but failed to delete it from all system maps and couldn't reinstall it again. Rebooted... The rest is history...
I guess phone thinks that it has a corrupted system and that's why it doesn't boot.
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Nikkka said:
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Click to expand...
Click to collapse
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
h t t p s://w w w . getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
(Bad site, sorry. While the info in this article might be ok, all at this site is not.
So better to search if the info can be found elsewhere.)
+ lots of more similar articles + videos. Almost too much really...
CXZa said:
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
+ lots of more similar articles + videos. Almost too much really...
Click to expand...
Click to collapse
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
I guess it will be a hard effort to make my phone work again. I seem to give it up. Unfortunately, sending the phone to Navon for refurbishing... would cost too much and phone must be sent by post (!!!). It is a great phone, but customer service at Navon is...
Nikkka said:
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
Click to expand...
Click to collapse
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Nikkka said:
I guess it will be a hard effort to make my phone work again.
Click to expand...
Click to collapse
Maybe not that hard if you're able to connect to PC... but..
(it looks like that at the moment I cannot make a connection either, LOL
re-installing the drivers probably fixes it, IDK, have to check it some day... )
---
That OTA update needed (at least) one program more (to be run as a service).
Did that too. And I also disabled the firewall that was blocking the connection. :laugh:
It just says that my system is up to date. (Changing version numbers etc. doesn't help).
The server response hints to http://europedownhw.mayitek.com/ site
that seems to be dead...
Navon...
https://forum.hovatek.com/thread-25956-post-155741.html#pid155741
Oh yeah? http://smartnavon.eu/smartphones/navon-t503 (not even an old model)
https://logout.hu/bejegyzes/cappa72/sp_flashtool_readback_kiolvaso_opcio_hasznalata_gy.html
https://itcafe.hu/tema/android_dual_sim_ket_sim_okostelefonok_topikja/hsz_16132-16132.html
[QUOTE
CXZa said:
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Factory Reset doesn't work. I mean that in Recovery Mode it doesn't matter how many times I do Factory Reset nothing happens.
I have no twrp. Only KingRoot was able to root my phone. TWRP said my phone not compatible with it.
Click to expand...
Click to collapse
Nikkka said:
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
Click to expand...
Click to collapse
While you're are letting go, you could read some stuff linked below. Good
instructions. What to do and what not to do. (Unlike at that "getdroidtips"
site I linked earlier. Some of the tips and articles there are total rubbish.
Mixed stuff copied somewhere else, I guess. Some might work, but not all.
Also they use wrong words in article names to get better Google rankings.)
SP Flash Tool + MediaTek MT65xx drivers download and installation guide including bricked devices
Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial (Might be useful with win8 too.)
Download SP Flash Tool v3 & v5 – Latest versions ( Tip: read to the end)
Remove, Disable & Uninstall MTK USB Drivers and inactive COM Ports – USBDeview (if having driver problems)
(And I also sent you some info in Hungarian already in the previous post. Backup etc.)
Again. just for fun sake, I tried again if my MTK tablet/phone would be recognized by SP flash tool.
No luck. Previously it wasn't a problem. Still, the adb/fastboot works okay.
So, some problem with MTK drivers. I have used SP_Flashtool, BeTools,, even older ones
like WiseLinkTool. And maybe some that were between those two.
Well, I don't have any good reason to fix those driver problems at the moment,
everything works ok, but still it kind of sucks.
Anyway adb/fastboot works okay. And that is the problem mentioned originally in the title.
So, does the fastboot work?
With fastboot, if it works, you might be able to boot some modified recovery without flashing and then maybe do some backups etc.
My adb driver package, mentioned in my signature has some options to remove the
old adb installations and the old (maybe problematic) values from the registry...
USBDeview is better choice in some situations though...