Related
When the ota hit my droid 2, I couldn't update because I deleted all those stupid apps like vznav, blockbuster, amazon mp3, etc and couldn't upgrade without reverting my cell to stock. I hear that if you have a rooted droid 2 with just some rooted apps and haven't deleted anything, you can use the ota or skip reinstalling 2.2.20.
I understand this is a common issue right now so here is how I did it successfully.
First Download these files as they are ABSOLUTELY necessary.
Motorola drivers for omap 3630
RSD lite 4.7 & patch (4.8 and 4.9 didnt detect the device on my pc)
2.2.20 firmware (stock at launch)
2.3.20 firmware (latest)
2. Install RSDLite by double clicking the RSD Lite.msi file you just downloaded.
3. Once RSD Lite is installed, copy the pst_flash.ini file you downloaded with the RSD Lite install file and paste it into C:\Program Files (x86)\Motorola\RSD Lite OR C:\Program Files\Motorola\RSD Lite depending on where your computer put it when installing. Allow it to overwrite the existing pst_flash.ini file.
3. Unzip the drivers folder you downloaded (32 bit OR 64 bit), then double click the Motorola Consumer Driver Installer application and install the drivers.
4. Plug in your phone to the computer via USB cable and pull down the notification bar and choose USB connection as PC Mode.
5. Open the RSDLite program by right clicking it and selecting Run As Administrator.
6. Click on the “…” button next to the filename box and select the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file you downloaded earlier.
7. Once it is selected, hit Start and wait for it to finish flashing the phone.
8. Once it is done, click on the “…” button next to the filename box again and this time select the BL_D235_cdma_droid2_Consumer_replacer_HSPart.sbf file you downloaded earlier.
9. Once it is selected, hit Start and wait for it to finish flashing the phone.
10. Once both have been flashed, your are back to the stock Android 2.2 firmware.
11. Load in recovery mode and reset to factory default.
You can either upgrade now over the air or you can load the sbf for 2.3.20.
1. Plug in your phone to the computer via USB cable and pull down the notification bar and choose USB connection as PC Mode.
2. Open the RSDLite program by right clicking it and selecting Run As Administrator.
3. Click on the “…” button next to the filename box and select the VRZ_A955_2.3.20_1FF_01.sbf file you downloaded earlier.
4. Once it is selected, hit Start and wait for it to finish flashing the phone.
5. Bam you have 2.3.20, now you can do a recovery factory reset and do your thing.
From what I have seen on the web, you can't use this sbf if you installed the OTA cause it will brick your phone but you can reflash this sbf if you upgraded using this sbf.
I do not know if you can just take your rooted phone with deleted apps and flash the 2.3.20 over your current 2.2.20. I do know the process I used worked without a hitch.
Edit: Hey guys, after the patch I noticed bad battery life and my battery monitor wouldn't open. Apparently you will need to boot into recovery and wipe the cache partition. All the links work.
Thanks for taking the time to write this up ! Much appreciated =)
Sent from my DROID2 using Tapatalk
so does this mean if i'm on 2.3.20 and want to go back to stock( and reflash to 2.3.20 is impossible??.... I'm doing this because i went directly from fission 1.2.1(stock band) to 2.3.20 and just want to make sure whether i have the latest kernels
This isn't entirely correct. If you use the 2.3.20 FULL FLASH SBF, you do not need to restore back to 2.2.20, or reinstall any missing applications. The full flash is the entire stock sytem, as well as the bootloader and the kernel. So you can start from any D2 on any previous firmware with any modifications (removing apps, installing custom ROMs, etc) and if you hook it up to RSD and use the most recent full flash it will restore you back to stock on the newest kernel/baseband and restore all missing applications, everything. The full stock flash will take you back to stock regardless of the state of your D2, including if it is bricked and stuck at bootloader. The extra steps are not needed
Also, RSD 4.8 and 4.9 do work, provided you have the latest motorola moto connect drivers installed. If you are having connection issues with RSD put the phone in bootloader mode (not recovery) before you connect it to the PC.
You were correct in stating that you can not receive or apply the OTA by itself without having the original system with all pre-installed apps intact.
is there a way to go from 2.3 to 2.2, like the original kernel and radio, baseband that most people were running like a month ago. im trying to sbf form 2.3 to the older one and i keep getting errors is there any way i can go back?
Not currently. The bootloader has been updated and will no longer accept the old kernel.
Sent from my DROID2 using XDA App
zibrah3ed said:
Not currently. The bootloader has been updated and will no longer accept the old kernel.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Thanks for the reply. now i can stop trying lol, it was driving me crazy.
bladearronwey said:
This isn't entirely correct. If you use the 2.3.20 FULL FLASH SBF, you do not need to restore back to 2.2.20, or reinstall any missing applications. The full flash is the entire stock sytem, as well as the bootloader and the kernel. So you can start from any D2 on any previous firmware with any modifications (removing apps, installing custom ROMs, etc) and if you hook it up to RSD and use the most recent full flash it will restore you back to stock on the newest kernel/baseband and restore all missing applications, everything. The full stock flash will take you back to stock regardless of the state of your D2, including if it is bricked and stuck at bootloader. The extra steps are not needed
Also, RSD 4.8 and 4.9 do work, provided you have the latest motorola moto connect drivers installed. If you are having connection issues with RSD put the phone in bootloader mode (not recovery) before you connect it to the PC.
You were correct in stating that you can not receive or apply the OTA by itself without having the original system with all pre-installed apps intact.
Click to expand...
Click to collapse
I gotcha, well it works exactly as stated so it was safe and is safe to do it the way I flashed. I will edit the sticky though to remove irrelevant info. Also reflashing the 2.3.20 sbf after flashing once yielded no errors. I'll edit the op.
Well I ran into big problems. I had 2.2.20 and wanted to sbf to 2.3.2 and it worked all the way up to downloading ram to bootloader and froze and got stuck and I sbfd back to 2.2.20 with no errors. Now my phone says the system is 2.3.2 but the baseband is still .05 and I tired to flash sbf to 2.2.0 today and I got the same downloading ram to bootloader and now I can't get even 2.2.20 to run on the phone. With this being said I got stuck on the bootloader screen(told me there were some errors and battery okay and plug in usb) so I figured id try to sbf to 2.3.2 and it came up with the same error of "downloading ram to bootloader and froze" and the phone restarted but now the M showed back up and is running normal now with the system 2.3.2 but still old baseband so idk what went wrong and why it wont let me get past downloading ram to bootloader. What's wrong because I've tried several times now and I just want the new baseband and bootloader. Please help me
Sent from my DROID2 using XDA App
you cant downgrade from 2.3.20 to 2.2.20 because of the updated bootloader. What OS are you using? What rds are you using? did you copy over the fix into the rds directory? You may have bricked your phone by tryin to downgrade =(. Have you tried loading your phone into recovery?
JonandRoid said:
Well I ran into big problems. I had 2.2.20 and wanted to sbf to 2.3.2 and it worked all the way up to downloading ram to bootloader and froze and got stuck and I sbfd back to 2.2.20 with no errors. Now my phone says the system is 2.3.2 but the baseband is still .05 and I tired to flash sbf to 2.2.0 today and I got the same downloading ram to bootloader and now I can't get even 2.2.20 to run on the phone. With this being said I got stuck on the bootloader screen(told me there were some errors and battery okay and plug in usb) so I figured id try to sbf to 2.3.2 and it came up with the same error of "downloading ram to bootloader and froze" and the phone restarted but now the M showed back up and is running normal now with the system 2.3.2 but still old baseband so idk what went wrong and why it wont let me get past downloading ram to bootloader. What's wrong because I've tried several times now and I just want the new baseband and bootloader. Please help me
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Make sure you use the FULL FLASH and not the system only file
Renegade8100 said:
you cant downgrade from 2.3.20 to 2.2.20 because of the updated bootloader. What OS are you using? What rds are you using? did you copy over the fix into the rds directory? You may have bricked your phone by tryin to downgrade =(. Have you tried loading your phone into recovery?
Click to expand...
Click to collapse
Im using RDS 4.9 there was no inf files that came with .9 so idk what you're talking about. I know 4.7 required a patch but idk if the new ones require it. I have fission 2.0.1 and my phone didn't brick because I have it up and running right now but I still don't have the new baseband mine is still .05...
Sent from my DROID2 using XDA App
JonandRoid said:
I still don't have the new baseband mine is still .05.
Click to expand...
Click to collapse
There's a tutorial on my "[TOOL] Ubuntu livecd" thread on how to update the baseband only, after flashing 2.3.2. Just go to the bottom of the OP and it will all be there. (I'd quote it but I'm on my D2 not my computer)
Sent from Newk's DROID2 using XDA App
No files
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
ameggs said:
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
Click to expand...
Click to collapse
This should help you out.
http://www.mydroidworld.com/forums/...rld-present-droid-2-2-3-20-triple-threat.html
ameggs said:
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
Click to expand...
Click to collapse
The update file in my tut still works for me. Update.zip
All the links should work. I just uploaded the 2.2.20 to include the drivers and rsdlite
bladearronwey said:
Make sure you use the FULL FLASH and not the system only file
Click to expand...
Click to collapse
FYI, I did the full flash for 2.3.20 because the automatic update kept failing. Not sure why it didn't work - I had rooted the Droid2, "removed" a few annoying apps by renaming the adk and odec files to .bak. I unrooted it and tried the auto update again but it failed. Not sure what was making it fail, but rather than put all the apps back and try letting the phone do its thing, I used the method above - just using RDS Lite to flash to 2.3.20 without doing the previous steps.
It worked fine, but I had to dial *22899 to re-activate the phone afterward.
So far so good, but I'm not sure that rooting the phone and messing around with it, to the tune of a few good hours of my life, was worth a little bit of battery life, especially considering the 2.3.20 is supposed to fix the two problems I had with the Droid, namely poor battery life and email sync problems after inactivity.
thanks for the how-to! i flashed straight over from a rooted 2.2 phone to the new version as well.
i did experience force closes on the battery monitor as well, and clearing the cache did not fix that. i cleared, rebooted, and when it still didnt work, i flashed the phone once more and all is well. did not need to clear cache a second time. im a rookie still at all this, so bear with me if my reply seems obvious- or doesnt make sense.
i also had to reactivate the phone with the *# referenced above.
thanks again!
Had no problems updating from 2.2 to 2.3 using only the 2.3 SBF. Worked great and kept all other settings intact.
To fix the battery monitor force closing issue; just plug your phone into the charger while it's on! Fixed the issue right up for me!
Okay soooo, SPECS.
- Android 2.2 froyo
- LG P500h (Koodo)
- Standard Rom
- KDZ won't open
Now, what I did, it was stupid. I wanted a black notification bar so I downloaded a file, it replaced the original framework file in the system files of the phone, I tried to open an app and it force closed so I restarted my phone and guess what? ANDROID BOOT LOOP!
First instinct. Re-flash the firmware with KDZ.
KDZ won't open? I don't know whats wrong... Someone help, please
.:EDIT:. Resolved, I updated throught the LG Update Tool and now im on 2.2.2 but I can't downgrade cause KDZ still wont open so i dont know how I'll be able to root again
Hey guys,
Like many T-Mobile G2x users i got seriously fed up with the poor gps K on the phone. When i first got my phone, after i rooted it I tried many of the roms here on the development forum but none of them could fix the gps locking issue. IN the past few days, the phone could not even "view" satellites at all. I was running the JUL 2011 baseband at the time. However after digging around, I went ahead and updated from the LG website with their update software. now my current baseband is M6600A-SCAUTNZ-2.0.9720T 1 [MAR 11 2012 10:00:00] MP:TRULGE_08.09.02R-MDM and gps functionality comletely came back. I have a lock under 1 min, the phone still works for calls/text, and data still works.
I ran this process on a computer with Windows 7 Ultimate 64-bit. After the LG update completes it will revert the phone to stock recovery.
Here is a step by step of what I did. Please read everything first before doing the steps.
1. Use TGA_Gunman's guide to restoring a stock Nandroid OS that is unrooted. http://forum.xda-developers.com/showthread.php?t=1048274
A Stock ROM (v21e, v10f, or possibly others) is required for the "LG MOBILE SUPPORT TOOL" to work. Either from a personal backup or downloaded. Recovery version doesn't matter, but suggested to have latest CWM to make Nandroid backups & restores easier.
2. (optional) After you boot into the system link your google accounts, just as you would when opening a phone for the first time.
3.Visit LG's Website and download the T-Mobile LG G2x software update tool.
http://www.lg.com/us/support-mobile/lg-P999 (click on the software update tab and follow the 4 steps)
4.After installing LG Update software on your computer, run it, and follow the steps it tells you exactly.
5.Have PATIENCE! This will take around 15 min. and patience is the key. Let it sit there and do it's thing. Make sure your computer doesn't turn off or go into standby during the process and don't disconnect your USB cable until the installer is at its last step and its tells you it's done with the update.
6. Enjoy your functional gps!
P.S.: Thanks to everyone for the helpful feedback and tips to making this guide better!
If you are looking to downgrade your baseband or have unknown baseband error check out xBkKx's guide http://forum.xda-developers.com/showthread.php?t=1680292
EDIT 06/2/2012:
The CM7 RC3 update has been verified that it will work with the new March 2012 baseband. If you wish to update to the rc3, apply a "dirty flash" of the 27th nightly update after it (this resolves the gps locking time back to a couple of seconds again).
CM7 RC3 Update link : http://download.cyanogenmod.com/get...t/archive/update-cm-7.2.0-RC3-p999-signed.zip
CM7 27th Nightly Build: http://download.cyanogenmod.com/get/jenkins/1991/update-cm-7-20120527-NIGHTLY-p999-signed.zip
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
You don't have to be on that nandroid or link your Google account prior to the update.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
xBkKx said:
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
Isn't there already guides to update the phone?
You don't need to be on that nandroid or link your account.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
Click to expand...
Click to collapse
When i said calling/data still works i was referring to what some other people in the forums had said that they couldn't get a signal after updating baseband. I, however, did not find anything about using LGs update tool on windows 7. All the topics that came up were about procedures on doing it with windows xp only.
If this way works with the other nandroid versions that thats great news . However, when i was on the July 2011 baseband and I loaded one of the other stock nandroid versions the earpiece and microphone were not working at all. I could place/receive calls but the other person could not hear me nor could i hear them. when I loaded the v10f stock this problem did not come up, so just to be safe I recommend using that one.
Also you said there's calling issues for people that want to use other roms with this baseband? Does that mean I can't load up one of the recent EB ICs roms, etc with this baseband version?
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
BuddhaTeh1337 said:
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
Click to expand...
Click to collapse
actually now the 27th CM nightly update and the CM7 rc3 update have fixed the in call audio problem. im running this update with the new baseband on my phone and everything is working fine. the only thing that doesnt work yet are the old ROMs .hopefully devs do something about that
I also updated from rooted stock (xboarders 2.3.3). I didn't go back to stock recovery. I just ran the LG updater (already had drivers installed), plugged in the phone, hit the update button, and let it do it's thing. It took about 20 minutes
I'm confused about all of the confusion.
XDA Mobile
Hi all,
I did the above procedure, and did the restore from the "LG-P999-V10f" image.
On reboot, the phone comes up and shows the stock "LG" boot up screen.
The scrolly thing goes across for a bit, and then *stops*!
At this point, it is locked up, it won't boot any further up, and when I attempt to use the LG Updater tool, it does see the phone, and says "Phone connected", but the 2nd part of it when checking the phone communication, it fails with "Problem with communication between the cell phone and PC".
So I am stuck...
(Hopefully not bricked?)
Any thoughts? Suggestions?
Thanks!
Scott
I figured it out, after some minor panic!
The problem was, my ClockWork Mod Recovery bootloader version on the phone was too old!
I used a factory ROM image that was taken from a newer version, and it included some (.tar's I think) file types that weren't supported on the old version of the Recovery.
Thus, I burned an incomplete version of the stock firmware to the phone!!!
(Which is why it was stuck at boot!)
I was able to "One Touch Recovery" with a newer version of Clockwork Mod, slap my Backup of my CM in place, and get back to where I started.
And as part of the "One Touch Recovery", it updated my boot loader to a newer version, and so now the loading of the factory ROM image worked.
I then just ran the LG Updater software after going back to the factory ROM Image, and indeed, it finally works as expected!
Scott
Glad to hear that it worked Scott! And thanks for the feedback, i have updated step 1 to say you need latest version of clockwork recovery
It looks like LG may have taken the update file down, or for whatever other reason, the software update tab is blank. Could someone put up a link to the update file?
@sigmabeta: I noticed during a particularly slow page refresh that the links for the usb driver showed up briefly as the page loaded, then disappeared. I managed to stop the page from loading completely and got the 4 steps listed (under manuals, of all places) one of the links was the update tool, here is the link:
h-t-t-p://csmg[dot]lgmobile[dot]com:9002/clientapp/B2CAppSetup.exe
I downloaded it successfully from there. Enjoy!
(sorry I'm new and it won't let me post links yet)
LG update tool won't update
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
aft3rgl0w said:
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
Click to expand...
Click to collapse
hmm. im not sure about this one. try this: reboot into clockwork recovery mod and do factory reset . after clear your cache, then clear your dalvik cache. then install the v10f from the restore menu in clockwork mod . after restart, set up your phone as you would do for first time (link google account to it) and then plug it in to your computer and run the LG update tool. thats what i did and it worked for me
also you said version v11f? you must have not flashed the restore correctly. do the above.
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Phone info SW ver says LG-P999-V10f. Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll re-download it again and try in the morning. what version of the LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
aft3rgl0w said:
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll redownload it again and try in the morning. what version of te LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
Click to expand...
Click to collapse
yes. you should do a complete factory reset even after installing the v10f rom. this is detailed on the original post on how to flash back to stock rom in TGA_Gunmans post.
I just noticed too that it reverted back to froyo (v2.2.2) and not GB, could this be part of the problem? should the stock be 2.3?
just to clarify your last reply re factory reset after v10f flash - should i clear dalvik as well?
yes it should revert back to froyo. and yes reset the dalvik cache too
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my phone
Sent from my LG-P999
xBkKx said:
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my
Sent from my LG-P999
Click to expand...
Click to collapse
yes you could try the 21e. however for me, that version always failed to download from the website gunman uses to host those files so i used the v10f inatead. much faster download.
btw how do you revert back to a previous baseband?
I just Googled how to do it using like 6 different guides :/ I edited my thread on iso help on it with what worked for me if you want to try it: http://forum.xda-developers.com/showthread.php?t=1680292
V21E/2.3.3 Mirrors, just restore it, connect phone to computer, run updater, should go smoothly :
Dropbox
MediaFire
RapidShare
I am trying to find a download spot for just the 2.2.1 hotfix (WiFi model). I have downloaded the full 2.2.1 but flashing the full 2.2 upgrade was a bit of a pain and I'd much rather just flash stock recovery and flash the update and reflash TWRP than to flash the full update and deal with Titanium Backup etc.
I flashed the 2.2 WiFi image on my LTE model when it first came out, and it's been great except my device shows it is "up to date" although it is not on 2.2.1. (the color gamut is is horrid 2.2 color and not the fixed one from 2.2.1).
TIA!!!
Nvidia has been postion ota links you can flash with cwm/twrp. You will need to reflash su as expected. I found it on the geforce forums... There were LTE us and WiFi us floating around and an explanation to what ota is right for the device you have.
Stumbled on it quicker than I thought.
WiFi us:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_515.3274.zip
LTE us:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29979_515.3274.zip
Sent from my SHIELD Tablet using Tapatalk
ben.nesheim said:
Nvidia has been postion ota links you can flash with cwm/twrp. You will need to reflash su as expected. I found it on the geforce forums... There were LTE us and WiFi us floating around and an explanation to what ota is right for the device you have.
Stumbled on it quicker than I thought.
WiFi us:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_515.3274.zip
LTE us:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29979_515.3274.zip
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
You are awesome, thank you !!!!!!!!!
I can't figure out how to find files at ota.nividia.com without knowing the actual file name and location. Drives me nuts the full ROMs are easy to find but the OTA seems to be some sort of secret thing.
Edit: see below, worked great.
The WiFi download is over 700MB, it's the full OTA and not just the hotfix. Why is the stupid hotfix so hard to find? Never experienced this with Motorola or Samsung. Samsung hides there stuff pretty good as well, but at least we have an independent site (sammobile) to provide us all the files.
Well it installed fine and with the su install I kept root. I don't know why the downloaded update is so large, looking in the zip I saw a new boot image (small), the new blob for the kernel (also small) and about half a dozen files under system. I also don't know why my device was showing up to date, other than perhaps the fact I am running the WiFi ROM on an LTE device and it's just confused.
Thanks again for finding the file for me, it was super fast and easy.
Please help me,
How to root freetel kiwami samurai and custom rom for it!
It is use android 6.0 not good
Any updates?
Kingo and kingroot work, but no custom roms. No twrp or any recovery for it either.
Would like to know if anyone has any ideas or news on this.
I'm looking at one of these on ebay right now, leaning towards buying it. I'd almost certainly buy it if I knew there were custom ROMs available.
For the price, definitely an amazing phone. It really sucks that there is nearly zero support for it anywhere.
For $120 I decided to grab it to replace my constant headache with our note 4 here.
The main camera, very, very nice.
The speed seems alright. The feel, the build is great.
The battery seems to drain kinda quick, but that might be my imagination.
I'm comparing it to our Y6Max and phab2 plus.
I used Kingo root on it initially, then went to and currently have kingroot on it. Kingo had annoying floating ads.. Kingroot seems decent but I'm suspecting that it has something to do with the battery drain.
Worst part for me at the moment, trying to work around not having twrp+xposed on it.
(the nav/status bar is taking up too much of the nice 6" screen)
If anyone has any way of getting twrp or something similar on it.... Please let me know - help us all out.
After some fighting with Kingo and kingroot, back and forth, I managed to get supersu to take over, install binaries and update... Now no more Kingo or kingroot. Tempted to try installing xposed, but I'll wait for now.
Found a command to enter in terminal to use full immersive mode all the time...
Adjusted dpi as well
Now the phone is looking nice.
Just gotta wait and wish for someone kind enough to help out with getting a custom recovery on these phones.
Really loving this phone
Stock rom for freetel kiwami FTJ152D
Hi all, I need stock rom or worked rom for my freetel kiwami FTJ152D.
Can someone upload this or what is the link to download this ?
I bricked my phone after flashing custum rom MM6.0 published on needrom. No touchscreen, very bad display, no imei, no root.
Please, help me.
meteor37 said:
Please help me,
How to root freetel kiwami samurai and custom rom for it!
It is use android 6.0 not good
Click to expand...
Click to collapse
Hi, I used kingoroot online and mine was rooted. (Freetel samurai kuwami FTJ152D stock rom 5.1)
But now, I have a big issues, I flashed it with a MM6.0 publshed on needrom and now there's no touchscreen, screen display very bad, no imei (impossible to put imei and root with few known method) and no root.
Could you please upload your worked rom ? Stock rom or custum but work fine.
Or where can I find link to download it ?
Please help me.
Myloverboy said:
Hi, I used kingoroot online and mine was rooted. (Freetel samurai kuwami FTJ152D stock rom 5.1)
But now, I have a big issues, I flashed it with a MM6.0 publshed on needrom and now there's no touchscreen, screen display very bad, no imei (impossible to put imei and root with few known method) and no root.
Could you please upload your worked rom ? Stock rom or custum but work fine.
Or where can I find link to download it ?
Please help me.
Click to expand...
Click to collapse
Seems like the rom on needrom was for a slightly different phone. However the phone is so cheap now its almost disposable ($100)
I have been able to get recovery but it is in microscopic Japanese Kanji, showing off the high resolution of the screen, but I can't read Japanese.
That is actually a diagnostic menu in chinese you went into (Google Translate FTW lol). For the stock rom recovery, you can turn the phone off, hold volume up button and plug in the usb cable that is connected to a computer. You can also hold volume up and power and let go of power as soon as freetel logo comes on. You will enter stock recovery that is in english but it is useless because you cannot use stock recovery to undo what you have done to your phone since there is no place online you can find a stock rom of this phone model (I have searched for many many hours online).
I am working on getting stock rom dump off my phone using sp flash tool but biggest headache for me has been the scatter file so far. Without it, I can't use the 'read back' option to extract an image dump of working stock rom. Only scatter file i found is from extracting the needrom MM 6.0 which is for the samurai FTJ152D.
I am unable to make a scatter file using MTK Droid tools since MTK Droid tools do not work for 64-bit mtk processors like the one in Kiwami. Scatter files are CPU specific but they are further modified based on the model of the phone and the android version of the rom, so the scatter file from MM 6.0 for FTJ152D is very close to what we need for FTU152D but even a slight variation will result in a rom dump that will not work. If any of you are willing to try, I can use the scatter file from MM 6.0 (FTJ152D) on my phone that is FTU152D to extract a rom dump, but keep in mind that this will probably not work and might make matters worse for your phone. Scatter files are sort of like 'Table of Contents', and if the page numbers are wrong you end up reading wrong chapter... (you get the idea).
I haven't found any other way of making a scatter file. If anyone knows how to get a scatter file from a phone running 64-bit processor such as MT6795, please help us out. Thanks.
Just an update, while trying to make a 'read back' dump using sp flash tool, I accidentally started a download of the FTJ152D MM firmware I was using the scatter file from... Needless to say now I have the demo version of marshmallow and have lost my IMEI info from phone. I did make a 'read back' dump of the phone before i messed up, using the guide from syserr about "Dump Full Rom" at
https://forum.xda-developers.com/showthread.php?t=2540400.
NOTE: If you are still on stock rom that the phone shipped with, DO NOT try upgrade using SP flash tool, at the very least you will loose IMEI information for both sim slots. For me, the phone connects with sim but I can only get 2g data speeds and make phone calls.
I am hoping that the following information can help others:
1) Most Important: If you root, do not use SUPERSU 2.79 or above versions or phone will be stuck in bootloader. Even if you make a backup of boot.img, sideloading it from ADB did not work for me, it kept failing. I am not sure if earlier SuperSU versions work or not, if they do work, make sure you disable auto update for SuperSU in Google Play Store.
2) Even if you make a backup of nvram.bin using sp flashtool, it will NOT restore your imei information in the phone because from what I researched so far, this information is populated using the BPLG and AP databases that are included with the stock firmware as separate files and quite possibly with 64-bit mtk processors, this information is protected and encrypted. Other possibility is that the nvram.bin i recovered from my whole rom dump is for lollipop and since phone is running on marshmallow, this bin file is invalid? I did try flashing two different nvram.bin (one i recovered from the stock dump i made when phone worked, another i downloaded from internet) using flashtool and it made the matters worse, all baseband info disappeared and both sim slots just totally greyed out in settings. If it greys out for you, just format the whole flash and flash the MM firmware again without any nvram partition. Just leave default settings for nvram in scatter file alone.
3) Currently, there is no way to root this phone when on marshmallow. Do not try the chinese one-click or other software such as miracle box, all the ones i downloaded and/or tried or not tried, were flagged by Anti-Virus as trojans and viruses.
4) Be very careful when trying to flash software on this phone, make sure you use the correct Preloader.bin file. The marshmallow firmware on needrom website has a preloader.bin file in it and it works fine. Do not attempt to try preloader from other similar phones or you will brick this phone permanently.
5) ADB and Fastboot commands do not help because the phone is not rooted anymore once you upgrade to marshmallow using the FTJ152D marshmallow firmware from needrom.
6) I have tried combinations of boot.img, and system.img from Priori 3 (it is also dual sim and rom on needrom website is android 5.1), was hoping for a miracle but no luck.
7) MTK Droid Tools works partially with this phone. Most options in the tool require root or do not work with mt67xx processors. I found mtk droid tools useful to enter recovery directly when usb debugging was enabled or to go to ADB terminal to try sideload or reboot bootloader to enter fastboot.
8) Even if you enable oem unlock in developers, the option (volume+up) in Fastboot menu to unlock the bootloader doesn't work. It seems that many MTK processors have this option disabled by the manufacturer.
9) TWRP custom recovery will not work with this phone because the 'boot script' (not bootloader) before actual recovery in the recovery partition has the touch disabled. I was able to get CWM to work by directly flashing it instead of stock recovery but installation of any zip files through recovery fail still.
10) I can confirm that the scatter file in marshmallow rom for FTJ152D available at needrom website has the right entries and address locations for our phone (FTU152D) because I was able to use that scatter file and a Hex Editor program (search for HxD on download.cnet.com) to carve out almost all the partitions from the 2gig partial rom dump I had of my phone in working state. When carving partitions from the dump, some trimming for certain folders is required because cutting the partition by size and making it a .bin or .image file will give errors in SP Flash Tool otherwise. The marshmallow rom or a Priori 3 lollipop rom, both can be used as a reference when cutting out the extra bytes.
If you are like me and have upgraded to marshmallow using the FTJ152D software, there are not many options. I haven't given up yet though, I backtracked my steps trying to make a backup of the phone in its current state using SP Flash Tool full rom dump and it was successful. If I could get my hands on full rom dump of 5 gigabytes of a working phone with lollipop software, I am confident I can restore my phone back to lollipop. This may not fix the IMEI problem but once the phone is running lollipop, it is possible to root it again using kingroot or towelroot and then use one of the imei repair apps or a program to rebuild nvram folder using the BPLG and AP databases and use root explorer to place it in the phone.
Phew... a long write but hope this helps others, and if anyone can help by sharing any thoughts or uploading their stock rom dump if own same phone (can read syserr's method of using 'read back' in SP flash tool to make one big partition dump for the whole rom instead of making seperate partitions which is a painstaking process.
Finally, some very good news for people like me who are stuck, figured out a way to root and install Xposed both Please give credit to Magisk and Xposed developers listed below.
Root:
Root this phone while it is running the FTJ152D marshmallow stock rom using the Magisk guide here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Follow the "Via Magisk Manager (Only support v14.0+): ... " method to install the magisk manager and the .zip file right through it. It patches the boot and makes a patched boot image that you can transfer to your computer and then rename it to boot.img and replace the original boot.img in the FTJ152D MM rom folder. Then use the SP Flash tool, load the scatter file in the rom folder and the 'Format all + Download' option in download tab (it will give you PMT error if you try to just flash the new boot.img alone). Hit the download button, turn the phone off, and connect it to the computer via usb. Everything else should be straightforward but if any issues, ask here, and I will try help if I can.
Xposed:
There is no touch support to make custom recovery work on this phone yet and the only custom recovery i got to work was an old version of CWM which behaved same like stock recovery and refused to let me flash zip files. The workaround I found that worked was 'Flashify' on Play Store. Now that root is working, flashify seems to work (tried Flashfire too but it just hangs and phone freezes). Follow the steps below:
1) Download and install the latest Xposed Installer Apk from their page.
2) Download the appropriate xposed zip file (SDK23 ARM-64), version 89 worked for me. Use Flashify to flash the zip file. If any issues come up, ask here and I will try help.
Official Xposed post is here:
https://forum.xda-developers.com/showthread.php?t=3034811
This post is also very helpful:
https://forum.xda-developers.com/showpost.php?p=67696847&postcount=2
All credits go to the respective developers for their work, including @topjohnwu, @rovo89, @mGforCe, @SolarWarez, @MaArCiN074 and others. Don't forget to thank them.
I also have been able to replace the demo mode logo with logo that was in the partial stock rom dump and will share it soon.
IMEI issue:
After gaining root and installing Xposed, a number of apps can help to at least temporarily get the IMEI written to the phone, that lasts till factory reset. One issue that people like me who installed the FTJ152D MM rom is that the bands in the phone are now based on the Japan region and almost all the frequencies and bands needed for phone to get 3g and 4g signal are disabled in the phone. From researching about this issue I found out (I may be wrong but that's the only information I could find and the bands that are enabled seem to confirm this), is that the latest mediatek chips come with all 41 bands and the phone manufacturers and operators disable or enable bands based on their regions and preferences, so that this phone, FTU152D is probably the exact same hardware as the FTJ152D and the only difference is the software which disables and enables the bands based on the baseband version of the rom. This is a problem for ppl like me living here in U.S but the enabled bands may be fine elsewhere. There is no way to change the bands as they are greyed out when you go to modem information though 'Phone Information' section (apps like 'Advanced Signal Status' can help access it). It doesn't allow me to select and enable band 4 and 12 as these are greyed out (but these worked before with stock rom, so I know the hardware supports them just the baseband version is wrong now).
Anyone know or can help get the right bands working, or have any hints to point me in the right direction, please post here. Thanks.
I was able to finish dicing up the raw dump to make back a working FTU152D stock rom with good baseband. Here is the link for instructions and download link:
https://forum.xda-developers.com/general/general/kiwami-samurai-ftu152d-stock-lollipop-5-t3750068
I have a question for any and all kiwami samurai owners /users. Is it just me, or does your WiFi seem to cut off regularly? I have been fighting with this from pretty much day one. When I'm using a sim card in the phone, I don't notice anything because the mobile data from the sim is working. But, I have 2 of these samurai phones now, and I bought a blackberry passport for my main phone and now both samurai phones are usually only using WiFi. Funnier thing... They both seem to have WiFi issues at the same time. How I know?... Well, I use an app on all of our phones and devices here - Zello. When the connection is lost, Zello sounds an alarm and lets me know. So if the phones are acting up, we'll hear this all day, disconnecting and reconnecting. I got one more for you, the disconnects seem much worse when I use the phones compared to just having them there sitting around. I even went as far to install many WiFi watching, locking, reconnecting apps to try and force the connection to stay on and alive. They have their work cut out for them seeing as when these phones decide they want to drop the WiFi connection, they will fight these apps to maintain WiFi connection until these apps pretty much give up. I have these as back up phones basically, so it doesn't matter so much but of course, this is extremely annoying and a huge inconvenience at times. Any one else out there experiencing this? The only thing I did do that may have a place in all this... Rooted the phones, and also I removed every google app. I have a note 2, note 4, doogee y6 Max, Lenovo phab 2 plus, tab s and an HTC one m8 that are all the same... Rooted and google removed. Playstore play services all that stuff - gone. Those phones don't act up anywhere close to as bad as these samurai phones. Many times I fight the WiFi off because doze and all that power save crap but these samurai phones are tough to figure out. Anyone have any ideas? I also froze and deleted a bunch of system apps(I know, I know) but that was only after I noticed the WiFi issue on the phone and was trying to see if possibly one of the system apps had anything to do with the WiFi disconnects or any power save features or control. So anyone.... Ideas?
J&G said:
I have a question for any and all kiwami samurai owners /users. Is it just me, or does your WiFi seem to cut off regularly? I have been fighting with this from pretty much day one. When I'm using a sim card in the phone, I don't notice anything because the mobile data from the sim is working. But, I have 2 of these samurai phones now, and I bought a blackberry passport for my main phone and now both samurai phones are usually only using WiFi. Funnier thing... They both seem to have WiFi issues at the same time. How I know?... Well, I use an app on all of our phones and devices here - Zello. When the connection is lost, Zello sounds an alarm and lets me know. So if the phones are acting up, we'll hear this all day, disconnecting and reconnecting. I got one more for you, the disconnects seem much worse when I use the phones compared to just having them there sitting around. I even went as far to install many WiFi watching, locking, reconnecting apps to try and force the connection to stay on and alive. They have their work cut out for them seeing as when these phones decide they want to drop the WiFi connection, they will fight these apps to maintain WiFi connection until these apps pretty much give up. I have these as back up phones basically, so it doesn't matter so much but of course, this is extremely annoying and a huge inconvenience at times. Any one else out there experiencing this? The only thing I did do that may have a place in all this... Rooted the phones, and also I removed every google app. I have a note 2, note 4, doogee y6 Max, Lenovo phab 2 plus, tab s and an HTC one m8 that are all the same... Rooted and google removed. Playstore play services all that stuff - gone. Those phones don't act up anywhere close to as bad as these samurai phones. Many times I fight the WiFi off because doze and all that power save crap but these samurai phones are tough to figure out. Anyone have any ideas? I also froze and deleted a bunch of system apps(I know, I know) but that was only after I noticed the WiFi issue on the phone and was trying to see if possibly one of the system apps had anything to do with the WiFi disconnects or any power save features or control. So anyone.... Ideas?
Click to expand...
Click to collapse
There are a lot of variables that could be causing your WiFi issues. Since it is happening on two identical phones, have you installed Zello on a different phone to notice if it happens on that phone at the same time as well? It is possible that it is your WiFi causing the issue more than the phones themselves. How far from the wireless router are you when this happens? It could be that the radio/antenna range on the Samurai phones is lower than other phones and when WiFi signal is weaker, these phones just disconnect. Also, in WiFi settings if you have changed 'Keep Wi-Fi on during sleep' from 'Always' setting to another setting? Another possibility is that 'Scanning always available' setting, if turned on, and you have uninstalled Google or system app(s) that interact with this setting, it could cause a bug where network is disconnected momentarily (see if this setting is on, turn it off).
How strong, how many bars does your WiFi signal show? Mine shows full bars up to 30 feet from gateway and at least half strength in my bedroom and WiFi is not affected or dropped even at half strength. Are you using 2.4Ghz or 5.0Ghz frequency? Try using 2.4Ghz as 5.0Ghz although faster, has a much lower range and if signal is weaker it does disconnect the phone to save battery life.
You could also check WiFi settings using the *#*#4636#*#* if it shows any issues in there.
Android# said:
There are a lot of variables that could be causing your WiFi issues. Since it is happening on two identical phones, have you installed Zello on a different phone to notice if it happens on that phone at the same time as well? It is possible that it is your WiFi causing the issue more than the phones themselves. How far from the wireless router are you when this happens? It could be that the radio/antenna range on the Samurai phones is lower than other phones and when WiFi signal is weaker, these phones just disconnect. Also, in WiFi settings if you have changed 'Keep Wi-Fi on during sleep' from 'Always' setting to another setting? Another possibility is that 'Scanning always available' setting, if turned on, and you have uninstalled Google or system app(s) that interact with this setting, it could cause a bug where network is disconnected momentarily (see if this setting is on, turn it off).
How strong, how many bars does your WiFi signal show? Mine shows full bars up to 30 feet from gateway and at least half strength in my bedroom and WiFi is not affected or dropped even at half strength. Are you using 2.4Ghz or 5.0Ghz frequency? Try using 2.4Ghz as 5.0Ghz although faster, has a much lower range and if signal is weaker it does disconnect the phone to save battery life.
You could also check WiFi settings using the *#*#4636#*#* if it shows any issues in there.
Click to expand...
Click to collapse
Thanks very much for the help....
so, the other phones( we have many) are mostly all set up the same way, all have zello...and no, they don't have the same issue disconnecting at the same time the freetels do.
The router here probably needs to be replaced but, cant get around to that for now.
a little update to this problem... I didn't want to try installing xposed before, because I didn't have recovery installed...got it done using flashfire. this got me xposed and I did this just for the hell of it since i didn't care so much about the phones since they were just being pains. However, after doing this, i also decided to install Lspeed. I remembered that I checked this app out before and i seen that It had some settings in it for tweaking wifi and Lnet. Not even sure what these would do, I started to mess around in there and toggled a few things on...just to see what would happen. also, i just happened to see something in xposed to download "Wifi regional problem solver". again, not sure what this would do, or if it would do anything, i said lets do it...installed it. and believe it or not, haven't had any issues like before with wifi since. Now, not sure what actually fixed the problem or if the problem is actually fixed or if it just took a break from driving me mad, but yeah...it's actually not a bad phone now.
as for Lspeed....using version 1.4.27(like this more than the latest for some reason) and I set up most things in the app to "balanced". not performance , not for battery. Under LNET Optimizer .... NET buffers : BIG. RIL tweaks enabled. NET TCP tweaks enabled. NET speed+ enabled. wifi scanning ...while i've always had off on all devices for as long as i can remember having androids...here in Lspeed i toggled on and set supplicant scan interval to 15secs and wifi idle ms to 1. left google dns off.
just if anyone wanted to know or cares ....and hey, maybe someone knows what any of that stuff means and might be able to say..hey, none of that would've changed anything so it's worthless....or maybe explain what each means or does and why it might have helped.
thanks again.