Tomorrow i send in my g1. and it is rc33 rooted, on the phone the htc person told me that they will inspect it to make sure there is not any 3rd part software on it for warranty void purpases. please help me! i need to get this done!
Just look for the stock firmware and flash it back.
Find the DREAIMG.nbh file and flash it to your phone.
i did this myself and it didnt autoupdate....am i missing something here??
ok i got RC7 and STILL no OTA updates.....and i cant do it through settings > about phone because the manual update thing aint there.....
Download anycut from the market , then open it and choose :
Activity
Device info
After shortcut is placed on desktop click press device info
Scroll Down until you see "Check for upgrades"
Hope that workes.
Hmmm I just tried what you said but no go..it says checking for updates then says check done and that's it... :/ when I scrolled up I noticed under build it had user ... is this meant to be something else or is it right??
as long as it's not rooted they don't care. as a user you can detirmine when you upgrade you phone just like linux some people like where they are at and wouild rather not upgrade. so they won't think anything of it if they get the phone back and it has RC7 on it
Ummm... I'm guessing 99.99999999% of G1s have 3rd party apps.
They include this handy app called "Market", which beckons most.
Call Bravo-Sierra on the tech and send your **** in - it won't be a big deal.
-bZj
down8 said:
Ummm... I'm guessing 99.99999999% of G1s have 3rd party apps.
They include this handy app called "Market", which beckons most.
Call Bravo-Sierra on the tech and send your **** in - it won't be a big deal.
-bZj
Click to expand...
Click to collapse
what the hell you on about?? and im trying to sort my phone out for diff reasons than above i just asked for a bit of help etc...i know full damn well about the market..i managed to downgrade but not upgrade to newer OTA's so i was after help...remember once upon a time you needed help too...
Just to be absolutely certain you should also restore the original SPL before flashing the .nbh file, just in case they check that part too
mrbishi said:
Just to be absolutely certain you should also restore the original SPL before flashing the .nbh file, just in case they check that part too
Click to expand...
Click to collapse
DREAIMG does not remove any custom boot splash screens. That will have to be changed manually as well.
Ok, im am trying to re-compile a SMG file that i have unpacked with unyaffs.
this is what i am trying to do before everyone starts shouting that you can just use a update.zip
Where i work we are about to start reselling Verizon Wireless under a different name, we buy our phones from Verizon.
i am trying to "de-Verizon" the phone and put some of our own customizations on it ie: Carrier text, boot screen ect...
any way, i need to do this in the least intrusive way so that i can show the AE's how to do it before giving to customer, or can be done by some one else.
The RSD-lite method looks the best, i have already successfully changed the moto logo and go that working, but now i am trying to edit the Carrier Text "eri.xml" in the stock load WITH OUT rooting.
Once i unyaffs the file i can do what i need to do but what steps do i need to take to compile it back into a smg file?
does anyone have a better suggestions for what i am trying to do?
Thanks, this forum has been a GREAT help
Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob
(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!
one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.
thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?
greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.
fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke
I recently got around to unlocking and rooting my Google Pixel 5, and now I'm wondering if it's possible to change the Google boot splash logo to an Apple logo?
(I used to run a rooted Samsung Galaxy S7 and I always loved having the Apple logo as my boot splash logo- thought it was hilarious).
I found the location at /dev/block/bootdevice/by-name/splash and was able to copy it to my computer as an image file (attached below).
However, I have no clue how to edit it as I can't seem to find a way to open it ("cannot open file as archive")
There was this forum that I found which told people to post their device name and splash image file so the OP can create a tool for it, but it seems to be inactive now so I'm kinda stuck (people have been requesting even to this date, but with no response from the OP).
Would any of you guys be able to help me out on this? Or should I forget about it cause it might be too dangerous to fiddle around with because I can very easily brick my device if a new boot splash image is incompatible?
Attached is the splash.img and what I presume to be the Google Pixel 5 boot animations that I found under /system/product/media
(Although it seems like my phone doesn't use either of them- might be because of the new Android 12 wallpaper based logo colours).
Hopefully someone smarter than me can assist me, I've been pulling whats left of my hair out for over 2 weeks of trying just about everything I can think of. I tried the flash tool website, doing the command line by line, flash-all.bat, and older versions of android back to 11. All I get is NO VALID SLOT TO BOOT (just like everyone else) One thing I have noticed is most of the files being flashed say something like "archive does not contain '(random file here).sig'" Could this be the reason for the no valid slot to boot from? Maybe a security signature?? I have linked my flash log if anyone cares to look. Also another no valid slot pic below. I really appreciate the help!
https://pastebin.com/SpUXuNmp
https://imgur.com/a/8h4DMfc
Nothing from your flash log pops out at me as abnormal, except the end where it says "File system raw not supported". Were you running a custom ROM before?
If you're just trying to get running again, I recommend using the Android Flash Tool again. Check the "Wipe device" and "Force flash all partitions" boxes.