Related
OK, so I have found a few guides that try to resolve this, but as yet nothing that completely got me where I need to be.
The background:
I have a UK T-mobile HTC Desire (Bravo) with HBOOT 0.93.0001, with an SLCD screen, with the latest OTA updates and now running MIUI ROM 1.5.13.
The problem:
Condensation under the screen meant that I needed to send back under warranty. To do this I needed to restore my phone to stock T-Mobile ROM.
I got hold of a stock T-Mobile RUU (available at Shipped Roms), tried to run this but got an error as the version of my current ROM and HBOOT was newer than what I was trying to put on the phone.
I did a bit more digging and realised that I was doing a few things wrong, did not have goldcard and realised that because I was on HBOOT 0.93 this would not work. Therefore I needed to downgrade HBOOT (http://forum.xda-developers.com/showthread.php?t=768256). This guide will put an unbranded RUU on the phone if followed completely, but obviously I needed a T-mo branded version and so used the RUU mentioned above.
This would prove to be my mistake.
This updated my phone to HBOOT 0.80 which unfortunately does not play nice with the SLCD screen.
Net result: my phone turned on (could feel the vibration when turning phone on).
Here is how I solved it....
The disclaimer:
This worked for me, it may not work for you ... etc etc .. I'm not responsible, etc etc.
OK, so to recap - I had:
- Created a gold card (TIP: always create a gold card by accessing your microSD in your phone over USB, I tried it in a card reader and it does not work properly)
- Downgraded to HBOOT 0.80 (http://forum.xda-developers.com/showthread.php?t=768256)
- Ran a T-Mobile Stock RUU (available at Shipped Roms)
The next steps:
- Go and get the latest T-Mobile OTA update (again, from Shipped Roms)
- Get your gold card (or create if required. Remember this must be done with the SD card in a phone, can be a different phone but must be your goldcard image)
- Rename the OTA update to update.zip and copy to root of SD card
You know need to boot in to recovery and run update.zip. All of this will be without the screen, so you need to follow the exact steps and make sure you wait where told - wait longer if in any doubt
- turn the phone off (battery out is sure fire way)
- Hold volume down (and keep held), press and release power whilst keeping volume held down (3-4 seconds)
- Now in HBOOT menu
- Wait 20 seconds
- Volume down * 1, press power button (phone go in to recovery)
- Wait for 30 seconds (reading SD card)
- Hold volume up and press power (go in to Android system recovery)
- Volume down *1, press power button (select "Apply sdcard:update.zip")
- Wait for 15 minutes (the update.zip on SD card is being read and applied)
- Press power *1 to reboot system
- After reboot you must wait a while and then you will see some green graphics on the screen... just wait it out
- You should then see the little pink circle and you can be happy
You will need to change language as the phone starts in German or Turkish, once done you will need to reboot to get everything completely back to English (some things such as vmail seemed to stick until reboot)
I hope this helps for anyone that was also terrified that they had broken their phone!!
There are also several methods for getting the phone in to USB debugging as it allows you to do much more with the phone and has some of it's own options to get you out of this mess. Obviously this requires going blind, these are the steps I went through:
- Turn off phone
- Turn on phone
- Wait until fully booted
- Press power and slide finger down to unlock
- Press and hold finger on screen until vibrate to verify you unlocked the screen
- Press back
- Menu
- Right 3 times, Down 1, click (Settings menu)
- Up *15 (to get to top of menu), down *10, click (Applications menu)
- Down * 3, click (Development menu)
- Click (USB debugging)
- Click (Confirm)
Hope this helps all!!
Cheers,
Pete
have the same issue with my htc desire but the problem is i have a usb brick so can't create a gold card.any help?
Hello!
Thanks for your guide. But for me it was a little different.
About my phone: HTC Desire with SLCD and T-Mobile Branding. S-Off via Alpharev
Preparing: Made a Goldcard out of my SD-Card with only one partition
Step 1: Downgrade HBOOT to original version (bravo_downgrade.img). Only necessary if you installed a Alpharev HBOOT.
Step 2: Downgrade the phone to Android 2.1 like here
Step 3: Install T-Mobile RUU. I used "RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe", you can find it at shipped-roms.com.
Result: No Black Screen, Downgraded Phone with original T-Mobile ROM.
I had problems with the RUU. So I started the RUU and found in the Temp-Folder the rom.zip. I renamed it to PB99IMG.zip, copied it on the SD and installed the rom in the Bootloader.
Cheers
Kobi-P
Hello!
I am hapy to share this link that I just found!!!
http://www.attdroids.com/forum/motorola-flipside-forum/3230-froyo-2-2-2-a.html
So, seems that the dream of having some custom rom could be more possible...
Personally I would like to thank the Moto people that take care to make approval for make this beta possible and for sure to the original poster in the ATTDroids forum, marvin and the others that are already testing it.
I will also copy a instructions resume of him (marvin) in order to get an idea of the process:
"For the best result from this upgrade I suggest:
Backup all your data from your various apps
use an app to backup your text messages if you want to restore them
make sure that you calendar and contacts are up to date on google so that they can be resynced
Make sure that you have all of your usernames/passwords handy
Factory reset your phone to clear everything out
install update
Do another factory reset (probably not needed, but it will not hurt)
set your phone up from scratch (setting up your WiFi connection first will speed up the initial setup)
Doing a reset first makes sure that you have enough space and that you don't run into issues with misbehaving apps after the upgrade. When the backflip was updated many users ended up doing a reset to clear various issues after they upgraded and you should at least be prepared with backups before you start the process.
The first thing that Moto support will advise you if you have issues after the upgrade is to do a reset.
Be prepared for some of your apps to not show up in the market after the upgrade. This is not just a Moto issue, but an issue for any phone that undergoes an upgrade because the market signature changes.
Waiting at least a week after the general release and reading the questions/problems that show up in the forums (especially the Moto support forum) is a good idea to prevent any gotchas.
MotoBlur will try to restore some of your settings when you enter your username/PW. If you want a true fresh start set up a new MotoBlur account."
I downloading by now and for sure will be try it asap. I use linux, so I will also check the SBFFLASH utility that I already used in my XT720 before and will test if would work fine in recognizes the FlipSide (I almost sure that it will do, but I will report if this may helps since I found more easy to use SBFFLASH since I didnt requires any installation of ABD or other stuff, only the litlle binary excutable and run also from a Live CD).
sbfflash download:
http://blog.opticaldelusion.org/2010/05/sbfflash.html
sbfflash instructions:
http://blog.opticaldelusion.org/2010/07/new-sbfflash-features.html
the main advantage of sbfflash is that it could be used with the original Moto Bootloader mode that loads sbf so it will help with flash with original Moto 2.1 ROM and then with flash of Froyo 2.2 ROM beta
Best regards!
Ok, some feedback...
Well did my test, and the phone works fine and found some quirks so I worte them at the en of this post.Also, I had to use the instructions at this link in order to get the update.zip menu option (because Moto page with instructions on update are down by now, so I may suspect that is something goes wrong with moto providing us with the final update at least we already have this beta working for possible future custom roms...), so I will try to post a collected list of steps for easy on another friends around...
Detailed Step list for update (copy and collected of other posts):
A) Backup Existing Data:
A-1) Backup all your data from your various apps
use an app to backup your text messages if you want to restore them
make sure that you calendar and contacts are up to date on google so that they can be resynced
A-2) Make sure that you have all of your usernames/passwords handy
A-3) Factory reset your phone to clear everything out
by using Menu->Settings->Privacy->Factory Data
A-4) Reboot, enter nomal and set the phone in USB debug mode.
by using Menu->Settings->Applications->Development
A-5) Turn Phone Off
A-6) B) Get Original 2.1 Eclair SBF file:
SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0 R_PDS001_SAGEATT_P033_HWp4_1FF.sbf
form this link:
http://www.mediafire.com/?l7i266ugb3pklxk
C) Install Original SBF file for get Full Stock Android 2.1 base
with Flipside Bootloader Mode - Restore with SBF File
C-1) Power Down Phone
C-2) Open the keyboard
C-3) Press and hold the up arrow key (to the left of the OK key)
C-4) Hold the power button down
and Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using SBF_Flash in LINUX or RSDLite in window$.RSD Lite version 4.9 works with the Flipside
C-5) Let phone finish and reboot without disturb (flash process may take around 8-10min and reboot may take 4-5min first time)
C-6) Reboot, enter proper data keywords for gain acces to normal menu.
D) Get Froyo zip with name:Blur_Version.2.159.17.MB508.ATT.en.US.zip
D-1) Download from this link:
http://www.filesonic.com/file/1597204534/Blur_Version.2.159.17.MB508.ATT.en.US.zip
D-2) rename the zip file to update.zip and put in the sd card.
E) Install update.zip for Froyo 2.2.2
E-1) Power off your phone
E-2) Open the hardware keyboard
E-3) Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
E-4) Press the key labeled Fn (lower left corner of the keyboard in landscape, upper left in portrait) and the T key at the same time
E-5) You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
E-6) Repeat previous steps for clean cache if You want (I did)
E-7) Repeat E-5 steps for option update.zip, and it will look for the file update.zip in the sd card and then start the upgrade. Let this to finish without disturb around 10-12min.
E-8) When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone, the phone will take around 12-15min first time after upgrade the update.zip
F-9) Reboot and start with registering process normal
DETAILS FOUND! PLEASE READ!
1) It could not by now to get access again to Fn+T recovery menu after update.zip install!!!!, please help if somebody could find if there another key combination after froyo update or if may be something else.
2) The update DETECTS Non-Original batteries!!! I have 2 batteries for my FlipSide and I just found that one of then that I bought by Ebay is NON-original and now the phone do not recognizes none charges it also (the battery was labled as original ,and in fcat WORKS AND LOADS FINE in 2.1 previously the update.zip).
Hope may helps, so please share your info & details about.
Best regards!
I found this info on Motorola sight for froyo recovery for flipside. Hope this helps.
Froyo
Power off your phone
Open the hardware keyboard
Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
Press the Up and Down Volume keys at the same time
You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone.
How does this open up the possibilities for custom roms? Does this unlock the kernel or something?
pre4speed said:
I found this info on Motorola sight for froyo recovery for flipside. Hope this helps.
Froyo
Power off your phone
Open the hardware keyboard
Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
Press the Up and Down Volume keys at the same time
You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone.
Click to expand...
Click to collapse
Hi!
Thanks for the info, tested and IT WORKS so, return back to 2.1 SBF is possible in case (I found previously the info about Fn+T keys combination and it works on 2.1 but no in 2.2, so glad that this VolumeUP+VolumeDOWN keys is working)
About custom roms from this, I previously was using an XT720 (but really need the hardware Keyboard and 850Mhz 3g Band in my country) so I goot my FlipSide for a solution, but, as far I remenber, one of the big troubles previously to tht XT720 got 2.2 was the fact that were no release, so the process that the Dexter dev had to use was a long Hack&Test Roms and codes from other model until got one working.
IMHO the fact of have a beta ROM that have tthe native harware support for the FlipSide may could make more easy to get a custom or at least "Enhanced" ROM (aka... crapware free, and with some useful touches like removing crapware & locking things as battery detection, overcloking, swap, more memory swap utils compatibilty, EXT filesystem supports, etc), but I am not a dev, so this is IMHO. And also I am happy that this beat at least reach the comunity, since is suspecting for me why Moto shut down the page about offcial FlipSide update and no more annoucements...
Thanks to all and best regards!
I have received info from a reliable source that downgrading the Flipside from the not-yet-released (or after it's release) Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Here is part of the communication I received:
Just so you know AT&T devices cannot be flashed back(downgraded). It will likely brick them. I would urge strong caution when flashing SBF files
Click to expand...
Click to collapse
marvin02 said:
I have received info from a reliable source that downgrading the Flipside from the not-yet-released (or after it's release) Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Here is part of the communication I received:
Click to expand...
Click to collapse
If your talking about essentially following this guide twice, it will not brick your phone. I followed this guide, flashing to fresh 2.1 then upgrading to 2.2. Then did my cousins phone for him. Without thinking it would cause problems I used my motoblur login on his phone on the 2.1 step to make things faster (not having to ask his info) and afterwards my phone as flagged unassociated with motoblur that i needed to contact tech help. To save myself the time on the phone I simply followed this guide again... flashing 2.1 on top of my 2.2, then upgrading to 2.2 again. All works fine. That was 2 or 3 days ago.
boazjuggalo said:
If your talking about essentially following this guide twice, it will not brick your phone. I followed this guide, flashing to fresh 2.1 then upgrading to 2.2. Then did my cousins phone for him. Without thinking it would cause problems I used my motoblur login on his phone on the 2.1 step to make things faster (not having to ask his info) and afterwards my phone as flagged unassociated with motoblur that i needed to contact tech help. To save myself the time on the phone I simply followed this guide again... flashing 2.1 on top of my 2.2, then upgrading to 2.2 again. All works fine. That was 2 or 3 days ago.
Click to expand...
Click to collapse
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
boazjuggalo said:
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
Click to expand...
Click to collapse
Yea I just did this and now my phone is doing the same thing...we are indeed BRICKED!! I'm working to try to solve this problem too. Let me know if you find anything as I can't figure it out! I really want this unbricked...I can't do ANYTHING!!
Well, finally I was able to return here after several very busy and hurry days.... too bad the issue of the bricked phones... really bad also that the info about the bricking risk was leaked several days after the beta sbf was leaked and that some of us use it on our phones.
However, I wonder about, if somebody may knows what could be the instructions of Moto Devs to the official beta Testers, that were on the beta testing process, for update their beta phones to the official Froyo after Moto ends their beta testing process... I suppose that tehir could be the official instructions to this beta testers so make their phones to normal froyos.
Anyway, I will ask the moderator of this forum to please change add the word OBSOLETE to the title of this thread in order to avoid more bricking issues, since is all that I could do by know since I am not a programmer that could help more about how to revert bricked phone.
Good Luck and best regards!
boazjuggalo said:
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
Click to expand...
Click to collapse
Ok Bud just discovered someone got the bootloader and sbf for us to unbrick! Here you go!
Froyo SBF and Bootloader for Flipside MB508 AT&T USA
Bootloader: BL_917B_4G_sageemu_Consumer_replacer.zip
Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com
SBF Flash :
Android 2.2.2 ------ Blur_Version.2.159.17.MB508.ATT.en.US
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
Download SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz for free on Filesonic.com
WARNING: ONCE YOU FLASH THE FROYO SBF ANY ATTEMPT TO DOWNGRADE TO ECLAIR MIGHT RESULT IN A HARD BRICK !!!!!
These files are made available as a general courtesy and I assume no responsibilty for your own actions.
Thanks for share, very usefull, and in fact, I could use it with success. Best regards
So, figured I'd attempt to root the thing today via the AAHK on my locked DHD. According to the effen manual, I won't need to gold card it beforehand either.
I went through the process, and I was told that the ROM that I had installed (2.5.3? Sense 3.0) had to be downgraded, so I went ahead with it. After downgrading, I was brought to an unresponsive bootloader. Being patient enough, I let it sit while I watched a movie, yet nothing happened after. I took out the battery and restarted it, and all I got was the Hutchinson 3G (my carrier) logo and it just stops there.
When I try booting in recovery mode to get to the bootloader, it does so, but it hangs.
After enough tinkering, I noticed the bootloader was only responsive once I rebooted without the memory card inserted. The phone itself is still inaccessible as it just stops at the 3G logo.
So far, I've tried to restore it through an RUU, but since it's still (I assume) carrier locked, I have to find the ROM that shipped with it. Unfortunately, I can't find a ROM that caters to Hutchinson 3G ROI (Ireland), so right now I'm downloading a UK version of it to see if it works. Apart from that, any recommendations on what I could do next?
Thanks :3
people are gonna need a little more info eg. what does it say on the boot screen s-off etc
what rom your trying to flash, formatted sd-card or not, possibly a corrupted download
AAHK does the business well, but can baulk at the slightest thing.
fairly new to some of this myself, but learning, my DHD took 4 attempts to finally do now on JT R4
Oh, mmkay:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011, 0:55:45
-----------------------------
Anything else I should include up there?
As for the ROM, I wasn't trying to flash anything bar the one that was downloaded through the AAHK client itself during the downgrade process.
After more tinkering, I've decided to leave it till today afternoon. Though I've made a few observations; so far
- The bootloader works fine when I turn it on WITHOUT the memory card
- The phone gets detected under the name "Android 1.0" when plugged in via USB both in hboot and fastboot. The fact that it gets detected I'll assume is a good thing
- Which leads to the second bit; it can be restored, since I've tried an Asian DHD ROM. It didn't complete because I was apparently supposed to find the appropriate ROM for it, which I assume is the H3G ROI version of it
- Aaand, the ROM still won't load up, and gets stuck at the H3G boot logo.
- According to the effen manual, it could be that my SD card was corrupt, so now my intention is just to merely restore it until I can actually afford to attain another memory card, which will be in a good few weeks and I don't wanna be smartphone-less for that period of time. But the only problem is; how?
if memory serves there isnt a rom in AAHK. the zip you intend using should copied be on your sdcard and initiated via recovery - vol down and on button. you should also be "s" off - did it offer to downgrade first [if needed]
from the manual
Insert the SDCard into the phone
Boot the phone
Turn on USB Debugging (Yes, plug it IN - use original cable plugged directly into the system board.)
IMPORTANT: Turn phone to charge-only mode. The phone stays in charge-only mode throughout this entire process. To make sure of this, check the default (menu > settings > connect to PC > charge only)
Win7/Vista: Right click on hack-ace.cmd and start as administrator (This will start the tool and bring you to the main menu)
option - 1
Install Clockworkmod
Clockworkmod version 5.0.2.7 -- yes
How to flash a custom ROM with ClockworkMod Recovery
Place the zipfile to be flashed on the sdcard. Do NOT unzip it.
Froyo disable Fast Boot: Menu > Settings > Applications > uncheck fast boot
Gingerbread disable Fast Boot: Menu > Settings > Power Options > uncheck fast boot
Turn phone off, no usb connected
Hold down vol- button, then press power to start, keep holding the vol- down button until Hboot menu shows up
Use the vol- down button to scroll down to recovery after some file checks are done (they will flash by quickly)
Press power to start recovery
Use vol down button to navigate, and the capacitive search button (bottom row of buttons, far right) to select
NOT VERY OPTIONAL/STRONGLY RECOMMENDED: If recommended by rom author or if flashing over another rom type (ex: cyanogenmod over anything else), wipe data/factory reset in Clockworkmod Recovery
Install zip from sdcard > choose zip from sdcard > select zipfile > Yes - (name of zipfile)
Repeat choose zip from sdcard for any add ons (gapps, themes, kernels, etc)
Press back button when flashing is complete until "reboot system now" is at the top of the screen.
Press power to reboot the system.
If desired, return the fast boot setting to ON in settings. (See above)
once yu crack it you'll see where you were going wrong
radio flashing is the easiest way to brick if you dont know exactly what your doing 99.9% of other stuff is recoverable
restoration is a more complicated path than rooting for noobs
I'm aware that there's no ROM included with the AAHK, I'm referring to the one that was downloaded THROUGH the AAHK when it said I'm gonna have to downgrade it beforehand.
And with reference to hboot, that's where another problem lies; my memory card is the one causing hboot to freeze. Hence, removing it prior to booting is the only way to get to it.
can you rerun AAHK and make a goldcard during setup and go that route -- wont help i know but being as its still "s"on you can return under warranty aslong as you dont send sim and sd-card tell them it wont go past h-boot.
if you have a card reader then format the card to make sure its clean, the drag and drop the required files on it - i have a lappy solely for this job with AV etc permanently turned off
Well, I'll rerun AAHK when I can find the SD card adapter, but since I've only recently moved house, it's gonna be near impossible until I get time off to unpack, which, till then, I'm still gonna need a functioning phone, so right now, I'm just looking for ways to return it to stock :3
i cant assist any further then as i've not yet RUU'd any devices as of yet.
hope you get it sorted
Thanks for trying anyways :3
I've been searching for an Irish RUU. Currently trying a UK version of it hoping it MIGHT just work. Anyone have more ideas?
Edit: Ok it didn't. Posted on the Three Ireland support boards trying to see if I can get an RUU
For a project, I needed a low cost 32GB tablet and noticed that Best Buy was about to introduce a new version of their 10 inch tablet. It is now available and I am creating this post to attempt to gather useful information into a single thread as I doubt this tablet will merit it's own forum.
What is possible so far...
1. Bootloader Unlock
Root Status
I tried Kingroot v3.5 and it was not able to root the tablet.
Links:
Specifications: https://www.insigniaproducts.com/pdp/NS-P10A8100/5855801
Manufacturer and Model: Lightcomm Technology Co., Ltd. MID1023MA http://www.light-comm.com/en/productinfo-176-193-75.html
Brief Review:
The tablet is pretty much what you would expect for a low cost tablet. The build quality is pretty good (it doesn't give much when you twist it, everything fits well) and the screen is better than I had expected. They had the old model on display and this is a pretty good improvement over the previous model. I may do a more complete review but just want to share some observations...
Camera - Low megapixel but fairly snappy response with autofocus.
Crapware - Very little - File Manager, FM Radio, and Sound Recorder - All else is standard android/Google apps
Storage - About 23 GB available (reports firmware is 9.19GB)
Speakers - Adequate but not very good
OS - Android 7.0 - May 5, 2017 Security Patch - No updates currently available
No problems getting ADB and Fastboot acess but will report more after I have time to work with it.
Saved for future use...
Bootloader Unlock
It is possible to unlock the bootloader. NOTE: This may void your warranty and the unlocking process triggers a factory reset. ALSO NOTE: Like many other devices, the tablet will display a warning at every boot that the device is no longer secure.
STEPS:
1. Enable ADB via Developer Options in Settings
2. Enable OEM Unlocking in Developer Options in Settings
3. Via ADB, reboot into bootloader mode
4. Ensure you are able to access the tablet via Fastboot
5. 'fastboot oem unlock' - Follow the prompts
6. Your device will reset (as it explains) and will be bootloader unlocked
Bootloader lock
It may be possible to relock the bootloader. When I gave it the command "fastboot oem lock", I got a message on the tablet asking me to confirm. However, it indicated that I *might* need to put the original software back on. At this point, I wasn't willing to try without a recovery option.
Hi. I just purchased the new flex 11 from BB myself. It appears to have the exact same processor, chip, and GPU as another tablet I have used before. The Lenovo Tab3 8. The only difference I can see is the emmc size (Lenovo 16Gb & Insignia 32Gb respectively) and the screen sizes. The processor is the same however limited to 1Ghz on the Lenovo whereas I believe the 1.3Ghz is the base CPU speed (I think the European version of the Lenovo came with a 1.3Ghz speed). So out of curiosity would the finished Lenovo's TWRP recovery work on the Insignia? Just a thought. Also, in case of brick could you use the Lenovo's firmware to flash it (after modding the scatter file of course). I'm just a noob to development but have no problem getting my hands dirty (I have 2 Lenovo's both broken but modified heavily)
I'm stuck in this in this problem, I can do the Bootloader Unlock but no furder. Is there any update for this device?
Is there a way to know if or when it will be possible to root this tablet?
Hidden Developer Mode
While browsing the net today I came across an article about unlocking the OEM so having a NS-P10A8100 I decided to give it a try and it worked.
Go to your about tablet setting, Model number and tap on it 7 times, a message will come up saying You are one step away from being a developer, this came up 2 times but after I did it the third time and checked my settings the new hidden Developer mode was in my settings and inside was a button, OEM unlocking.
I haven't tried anything else yet as I am new to all this but maybe this will help to get a Root Strategy for this model of tablet.
So it's there a way to fix this piece of sh!!! Cause it's so anointing that you can't even look at it with a ugly face cause it will start to stall.. I'm new on all this stuff so if there is away to fix it or making a little better please put all the steps to do it... Thank you so much!
flash file for this device?
* Prelude
What started this journey was noticing that Tasker had restricted call screening
to android versions 10+. I would be delighted to hear what techniques fellow
forum members use to fight spam calls. I am a complete beginner, and so I
thought I would detail my journey in case it proves useful for others. There is
some outdated information and plenty of online tutorials, it just takes some
time to sort it out.
I have a Huawei P20 lite ANE LX3.
* Unlocking the Bootloader
I believe this is by far the most tedious step. Now that I am free from carrier
contracts, I know that my next phone will not be from a manufacturer with a
locked bootloader. In any case you may have some luck emailing Huawei directly
or through paid third-party services. What worked for me was potatoNV
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
The documentation on the repository is perfectly fine. Specifically in my case,
the device first showed under device manager as 'USP SER' and I had to reinstall
the test point drivers (found in the above README) for it to turn into 'Huawei
USB COM 1.0.' PotatoNV did its job and I managed to get my unlock code.
* Project Treble/GSI? Fastboot? ADB?
Again, being new to all of this, I did notice a lot of noise when searching
online for information. The most informative links I found useful:
- https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
- https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
- https://developer.android.com/studio/releases/platform-tools
What is worth repeating is to USE THE GOOGLE PLAY APP 'TREBLE INFO' over the
more popular 'Treble Check', which falsely informed my that I needed an A image
rather than being fine with an A/B image. This wasted a lot of my time.
Initially I went down the route of using TWRP to flash the image, but this led
me to a soft brick (could very well be my own fault). The phone was frozen to
the TWRP splash screen, 'adb reboot bootloader' would not work. Power plus
volume down or volume up also had no effect. With no access to e-recovery or the
bootloader, I had really dug myself into a hole.
* Unscrewing a bricked phone
My last chance at fixing this consisted of getting the stock service firmware.
[NO ROOT] [BOOTLOADER LOCK] How to install an update [DLOAD Method]
I'm very happy :D:D After spending a lot of time trying to figure out how to install an original firmware using the dload method, I managed to find a guide that explains how to do it and today I will report the main steps: First of all, we need...
forum.xda-developers.com
This forum thread was useful and on unscrewing the situation. The real useful
part of the above link was the 'Software Upgrade Guidelines' documentation.
So ultimately what unbricked my phone was following the direction to press all
three buttons (power, volume up, volume down) at once to enter "automatic
upgrade mode." I gather this was supposed to utilize the 'dload' folder I copied
over earlier. As an aside, it was a lifesaver that 'adb shell' gave me access to
some unix commands to make poking around easier. The automatic upgrade using the
'dload' folder failed.
BUT RESTARTING FROM THIS "AUTOMATIC UPGRADE MODE" GRANTED ME ACCESS TO RECOVERY
MODE VIA THE POWER BUTTON + VOLUME UP whereas before this was not the case. By
the grace of God this allowed me to download a recovery image from Huawei
servers. How much longer will their servers retain this image? I don't know, but
I'm grateful either way.
* Lineage OS successfully flashed
What instead worked for me was flashing the "GSI image without TWRP" - from the
2nd of the 3 links above. This is the image that I used:
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
For sake of completeness M Rahman's 2018 article was still mostly accurate, the
'-u' flag may be omitted from 'fastboot -u flash system name_of_system.img'. The
only other thing I would append to his instructions is -AIF-'s recommendation to
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow
warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe
data/factory reset'.Reboot . - From:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I say this because I had seen the power button + down volume/up volume technique
yield different results depending on whether the phone was connected to the
computer. I suspect this is the fault of HiSuite, but who is going to track down
a bug like this?
* Evaluation
Pros:
- I had solved my initial problem.
- The new phone feeling!
Cons:
The most noticeable deficiency was that adding an external SD card AS SYSTEM
STORAGE would never finish; I gave it about a day before giving up.
I will add further reports as they come up.
In conclusion I give props to Huawei for keeping that server image alive, but
last I heard they were pivoting away from smartphones into clean energy
altogether. If I were to do it all over again, I'm not sure it would be worth
it. This took a good day's worth of time.
Big thanks to the AOSP developers and the XDA community for buying
my old P20 lite a bit more time. I'm also interested in which companies the
community considers friendly to "popping the hood"/tweaker mentality.
Hope this was helpful for someone,