Greetings Everyone,
We have a team over at thriveforums (.org, not .com) who are trying to root the toshiba excite and we need help. If there were a Toshiba Excite thread here on XDA I would be putting this there.
Things we know:
-From the box, toshiba excite is able to be temp rooted through ADB via:
Code:
$ tputimg --des ../data/local.prop
$ echo 'ro.kernel.qemu=1' > ../data/local.prop
$ exit
[email protected]$ ./adb reboot
The only problem with this is that we get screen errors that looks like a boot loop, but is simply a jumpy screen. ADB still works.
-We cannot remount /system as rw because of sealime.ko, a kernel module which is loaded in init.rc that protects that partition. A modified boot image can remove this.
-We can't try modified images without a recovery or else we could brick the device without being able to flash the original boot.img.
-There is no fastboot.
-There is no flash_image.
-We cannot port any recovery image (including Clockworkmod via builder) because... (see next)
-We cannot flash anything to any partition other than the original images we pull from /dev/block/mmcblk0p1 and mmcblk0p2 (Recovery and Boot, respectively). I have used split_bootimg.pl to pull them into kernel and ramdisk.gz files, and made it again with mkbootimg and it works. But, once I decompress the ramdisk files things go to hell. I've used various guides I've seen to do so, but when I flash it back to the device the device doesnt accept it.
It seems the problem has to do with the compressed ramdisk file. Once you open it up then try to recompress it, it doesnt like it.
Things we don't know:
Is there another way to compress this file?
Is there a special option I should be using? ( --base, and I've used the other info from split_bootimg.pl)
**Edit**: I followed instructions according to http://b.oldhu.com/2012/02/16/how-to-unpack-and-repack-android's-boot.img-correctly/ and found that the
--base option should equal 0x10000000
Does anyone have any other ideas?
We need help here and i'm yanking my hair out. This is a beautiful (despite the slight screen leaks) quad-core tablet that I do not want to give up on.
**EDIT**: I have confirmed the problem. The issue is during the unpacking of the ramdisk:
If I:
1. Split the recovery image
2. rebuild the recovery image as is
Then
Everything is GO
But, if I:
1. Split the recovery image
2. Decompress the Ramdisk
3. Recompress the Ramdisk (no edits)
4. Rebuild the recovery image as is
Then
Everything breaks.
**EDIT** With help from Fuses, it seems that there is bytes of code that look like a signature that is generated outside the normal compression.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~WHH
and where next?
I looked at the Hex code from a recompiled recovery to the original recovery. Everything's different including the kernel. Which I think means there is some special way to compress is that we need to get from toshiba. Or, that theres an encryption.
Man I wish we could get toast on this Im sure he would love a good challenge
I wish you guys the best +1 on this.
Sent from my SPH-D700 using Tapatalk 2
Do u have an excite tablet?
t1nk said:
I wish you guys the best +1 on this.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
---------- Post added at 03:40 PM ---------- Previous post was at 03:26 PM ----------
who developed the compression method used? Can toshiba have the right to change the program to have some encryption incorporated. Or is it some new way of compressing developed by the android source team used in ics?
I dont understand the roadblock were up against.
maybe a little more knowlege on the subject would enlighten me
An Email:
We would like to inform you that the source code which
you have requested was shipped out to your designated address.
Here is the shipping details as follows;
*Ship via : UPS with YAMATO
*UPS tracking number : *********
*Ship date : July 3rd, 2012
*ETA : within one week
*Description of goods : CD-ROM
*Quantity : 1 pc
Thank you for your patience.
Yours sincerely,
Get mine next week
We would like to inform you that the source code which
you have requested was shipped out to your designated address.
Here is the shipping details as follows;
*Ship via : UPS with YAMATO
*UPS tracking number :
*Ship date : July 3rd, 2012
*ETA : within one week
*Description of goods : CD-ROM
*Quantity : 1 pc
Yours sincerely,
Linux Section of
| TOSHIBA DIGITAL MEDIA ENGINEERING Corp.
| _________________________________________________
| | Linux Information for TOSHIBA PC Website
| |http://linux.toshiba-dme.co.jp/linux/index.htm
Will that help us root?
Just wondering if having source from toshiba, will help us root
I'm surprised there is no root yet...and by surprised I mean disappointed lol. I wish I knew something to try and help out. Oh well, good luck
Sent from my AT300 using Tapatalk 2
wayneb02 said:
I'm surprised there is no root yet...and by surprised I mean disappointed lol. I wish I knew something to try and help out. Oh well, good luck
Sent from my AT300 using Tapatalk 2
Click to expand...
Click to collapse
+1!
Well, Fuses from the Lazypanda people believes its something that has to do with gzip. As in: a) different compression levels, or b) different version.
The different levels all compress to the same size, so I believe i can safely say that that is not the issue.
Unless I go through and try install/reinstall every other version, I can't test them.
I think there is something of a signature or hash that is being used. But, I am by no means an expert. I wish one of the smart devs (like the people who rooted the SGSIII) could hop on this, because I've been past my experience limit a long time ago.
News from DALEPL:
OK, I got some good news and some bad news... First the good news... I now know why we canot load an alternate recovery or modified boot image... Now the bad news... Toshiba has locked the bootloader, so if there is any change, it will not boot. I talked to a Toshiba Engineer and he let me know this. There is a brite side, but only a shimmer at this time. Several of the engineers have spoke up about this. The engineer asked me if there were any other tablets with unlocked bootloadres. I told him Asus and Acer are. He said that they (engineers) have sent a message to Toshiba Corpotate and asked about providing an unlocked bootloader, but they have not received an answer yet. What I am trying to get accross is that we do have advocates within Toshiba, but they too may get nowhere with this.
We talked about the fact that DRM will not work on a rooted device. He said he under stood this and this is what they conveyed to Toshiba Corporate. Only time will tell. So, as it stands, we would have to get an unlocked bootloader in order to get the device rooted.
Click to expand...
Click to collapse
Whthacker I think you would be a good candidate to request unlocked bootloader.
from what ive seen u communicate very well on the forums, you get your point accross, I think you should ask the for the unlocked bootloader. I think u would have as good a chance as anyone.
(what good is giving us the source code with out anyway way to use it on the device) because of the locked bootloader
They want us to be guinea pigs and look for loopholes that could or (as in cases now couldn't) help... For what I use it I have looked for an unrooted solution (as far as going usb tethering to get tcp) and use it as a display, but I noticed that C97 dual core runs Air Display just as good. Why spend the $100 more? Custom bikes & cars won't see a difference, well on price - cheaper -
nothing new on this?
Petition to Toshiba
No new updates yet. I've started a petition to Toshiba to unlock the bootloader. I would appreciate everyones signature. Thanks a lot.
https://www.change.org/petitions/to...tloader-on-the-toshiba-excite-line-of-tablets
matt11601 said:
No new updates yet. I've started a petition to Toshiba to unlock the bootloader. I would appreciate everyones signature. Thanks a lot.
https://www.change.org/petitions/to...tloader-on-the-toshiba-excite-line-of-tablets
Click to expand...
Click to collapse
Signed.
Was the 100th petition signer.
Hope we get somewere with this
Signed it last night. Hopefully we get enough signatures to make them reconsider
Sent from my Galaxy Nexus using Tapatalk 2
Related
What I have tried:
SuperOneClick (all versions) <-- Siege Tanks Were Doomed
Gingerbreak <-- Just sits there
Z4Root <-- doesn't do anything
Rageagainstthecage <-- doesn't work
tried flashing Clockwork mod via tcard like works for the ZTE Blade, phone pretends like it is working then reboots and no change, trying to start using the power button and vol - yields nothing.
tried cooking my own rom with the kitchen make the update.zip file
Do adb reboot recovery
the phone comes back to the android system recovery <3e>
I select the option to do update.zip from sdcard
I get:
verifying update package...
installation aborted...
I need root access to remove the AT&T preloaded apps that won't uninstall won't stay killed and are hogging all my space on the phone (limited storage). I would also like to be able to upgrade to 2.3.7 from my current 2.3.4 and possibly make my own roms.
I have emailed ZTE Chinese support to see if I can get an non pork filled rom the Indian who answered their tech support line didn't have an answer and told me not to flash the ZTE roamer rom (if I could even find it) because it will brick my phone. They have been no help!
What am I doing wrong in the android recovery (I have tried both installer scripts)? Is there a way to rebuild the system.img from the system folder that was created in the kitchen because I might be able to rebuild it into the .bin file that the phone will accept from a sdcard with the built in update feature?
Ok so I figured out how to repack the system.img I then dropped it back into the folder and used zte-pack.exe to build my .bin file. I go to the tcard update and it fails verification...is there a signature that needs to be made? I didn't see an option in zte-pack
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Not sure if there is away as of yet. Just did a fast search and it seems no root has been done for it yet
try another time z4root
I am unable to root my XT928 either...Good Luck!
Apo11on said:
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Click to expand...
Click to collapse
I am soooo close just need that extra little bit of help, I will get it and when I do I will definitely share. I've only had a droid for 2 weeks and I have come this far, I am not going to stop. I have a BS in Computer Science and used to be a MCSE, I don't know this tech well enough yet but I will. Just hoping someone on here has the skillset I need to help complete this,
primanka said:
try another time z4root
Click to expand...
Click to collapse
tried it multiple times as I have with all of the one click exploits and custom rom trials
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
jcase said:
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
Click to expand...
Click to collapse
Thank you kind Sir! jcase to the rescue again - spent a couple of hours with me and busted this thing open. I can confirm my AT&T Aveil ZTE Z990 is fully rooted now. Mad props to jcase
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
jcase said:
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
Click to expand...
Click to collapse
Just woke up and saw this...can't wait to test thanks. PM Sent
I can confirm it works..I am now rooted!
jcase said he will post later... was able to remove the annoying at&t apps and gain back 30mb using titanium back...now to learn how to flash a custom rom...
http://www.androidpolice.com/2012/0...e-avail-att-offer-quick-and-easy-root-access/
enjoy
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
schoolage said:
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
Click to expand...
Click to collapse
we know about this - i'm fluent in russian. none of their file links work - it's an old thread on 4pda forums. you can use translate.google.com or several other engines, to translate web pages in real time.
according to ZTE although they share the same model numbers they have different radios (IE GSM / CDMA) and flashing the roamer to the avail will brick it. Apparently ZTE has not gotten the concept of using distinct model numbers yet...
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
theloon said:
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
Click to expand...
Click to collapse
How did you run Titanium Backup without installing a su binary?
shimapan said:
How did you run Titanium Backup without installing a su binary?
Click to expand...
Click to collapse
It just worked, even after a fresh flashing of the T card image.bin from ZTE.
Oh and heres a little batch file with needed files to automate jcase's procedure.
Sorry guys. I was hoping there was a backdoor that I may have missed to get this to work. After working with a couple folks there is no way to make this a user friendly install even with the corrected partition map info. As soon as you guys get unlocked I will revisit this and I will be checking back on a regular basis.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am looking at yet another Universal release. This time it's not a universal MotoBlur ROM but a possible Universal Ubuntop/Webtop+ release but I need testers. It is based on the latest Webtop release for the Photon (WT-1.2.0-180) and is successfully running on the Atrix, Electrify and Photon. We've been running Ubuntop/Webtop+ since September with minimal issues and I have received multiple requests to port. If successful, the advantage of this universal release is that any improvements and enhancements will carry over to all devices.
Prerequisites:
Unlocked
CWM Recovery (Bootstrap MAY work)
GB Blur based ROM with Webtop support (for now)
/osh be located at /dev/block/mmcblk0p13 (if osh is not located at mmcblk0p13 PM me with the correct partition location)
/osh be atleast 755.9MB
Not afraid of using terminal
Latest version of 7Zip
Ubuntop.7z - 264.3 MB (MD5- AA02B21D7A8D733621AD48B1425E95C8)
DO NOT POST RESULTS - PM ME YOUR RESULTS - IF THIS WORKS I WILL BE RELEASING TODAY
Installing:
Make a full backup including webtop (this is key so you can revert any changes)
Extract the UbunTop.7z file (this requires you have the latest version of 7zip installed)
Copy the Ubuntop folder to internal storage (again this is a must)
From CWM recovery, flash the Univ_Ubuntop_v1.0.0.zip
Reboot and launch webtop
Follow the instructions in the "READ ME!!!" file in the Ubuntop folder
(Right now I'm looking for install success and menupatch success. If you want to install applications and report on that as well that's great.)
Haven't slept in over 24hrs and just realized I need to use Aroma Installer. Gonna get some sleep, fix and reup Universal Ubuntop. For those that know what they are doing, edit the scripts to point ot the proper partition to play with it.
Hi, I sent you a pM as well, but I think you want the webtop partition which is not usually called /osh on our device. the block is mmcblk1p24
Lokifish Marz said:
Sorry guys. I was hoping there was a backdoor that I may have missed to get this to work. After working with a couple folks there is no way to make this a user friendly install even with the corrected partition map info. As soon as you guys get unlocked I will revisit this and I will be checking back on a regular basis.
I am looking at yet another Universal release. This time it's not a universal MotoBlur ROM but a possible Universal Ubuntop/Webtop+ release but I need testers. It is based on the latest Webtop release for the Photon (WT-1.2.0-180) and is successfully running on the Atrix, Electrify and Photon. We've been running Ubuntop/Webtop+ since September with minimal issues and I have received multiple requests to port. If successful, the advantage of this universal release is that any improvements and enhancements will carry over to all devices.
Prerequisites:
Unlocked
CWM Recovery (Bootstrap MAY work)
GB Blur based ROM with Webtop support (for now)
/osh be located at /dev/block/mmcblk0p13 (if osh is not located at mmcblk0p13 PM me with the correct partition location)
/osh be atleast 755.9MB
Not afraid of using terminal
Latest version of 7Zip
Ubuntop.7z - 264.3 MB (MD5- AA02B21D7A8D733621AD48B1425E95C8)
DO NOT POST RESULTS - PM ME YOUR RESULTS - IF THIS WORKS I WILL BE RELEASING TODAY
Installing:
Make a full backup including webtop (this is key so you can revert any changes)
Extract the UbunTop.7z file (this requires you have the latest version of 7zip installed)
Copy the Ubuntop folder to internal storage (again this is a must)
From CWM recovery, flash the Univ_Ubuntop_v1.0.0.zip
Reboot and launch webtop
Follow the instructions in the "READ ME!!!" file in the Ubuntop folder
(Right now I'm looking for install success and menupatch success. If you want to install applications and report on that as well that's great.)
Click to expand...
Click to collapse
How can I get this on the atrix 2
Sent from my MB865 using Tapatalk 2
chiikko561 said:
How can I get this on the atrix 2
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Seriously, I am pretty good about helping people out, but this does say right at the top that you basically can't.
On another note, have you talked to jimbridgman, if anyone can help you it's him
Atrix users have been begging me since September to get this on their phones. Unfortunately without any support from the community it wasn't until I sold off stuff for multiple projects that I was able to get an Atrix. After that is was fairly easy to get them on a unified webtop base. As long as I keep under 755MB it should port with no issue once the Atrix2 gets unlocked.
The Atrix/Photon are on Jaunty so the next step is to pull an updated webtop base from another device and get it running on the Photon. After that I can gut it and hopefully get it to fit on the Atrix (it really does require both the atrix and photon to get it to work). In short if I can't shrink it and get it running on the Atrix it's a no go as a unified base is the goal.
I was able to get something close to Ubuntop on the Atrix2 today but it requires a "hard way" method that would limit it to advanced users only. Making it harder is the opposite of where I'm going with this. It really requires unlock to make it a user friendly release.
Lokifish Marz said:
Atrix users have been begging me since September to get this on their phones. Unfortunately without any support from the community it wasn't until I sold off stuff for multiple projects that I was able to get an Atrix. After that is was fairly easy to get them on a unified webtop base. As long as I keep under 755MB it should port with no issue once the Atrix2 gets unlocked.
The Atrix/Photon are on Jaunty so the next step is to pull an updated webtop base from another device and get it running on the Photon. After that I can gut it and hopefully get it to fit on the Atrix (it really does require both the atrix and photon to get it to work). In short if I can't shrink it and get it running on the Atrix it's a no go as a unified base is the goal.
I was able to get something close to Ubuntop on the Atrix2 today but it requires a "hard way" method that would limit it to advanced users only. Making it harder is the opposite of where I'm going with this. It really requires unlock to make it a user friendly release.
Click to expand...
Click to collapse
Can you PM me the steps? I am our webtop/linux guru here, and I am the one that was able to get it run on our SDcard, and get full ubuntu access for the community and I made a full shell script to handle it all for everyone on the Atrix2....
I may be able to make it work very easily for everyone.
P.S. I am pulling this down now everyone, and I will play with this in the morning, and see what I can get setup for us, maybe I can include the whole webtop SDcard hack as well as have it auto start gnome for everyone right out of the gate.
I will keep everyone posted later tomorrow.
jimbridgman said:
Can you PM me the steps? I am out webtop guru here, and I am the one that was able to get it run on our SDcard, and get full ubuntu access for the community and I made a full shell script to handle it all for everyone on the Atrix2....
I may be able to make it work very easily for everyone.
Click to expand...
Click to collapse
lol. I told you Jim would know as always. I'd like to see too. I have never really used web top, but this is great
Sent from my MB865 using xda premium
Sooo... I personally wanted to change my boot logo.bin just like i did on my 1+1 and moto-x 2014
i typed around searching and reading for the tools and commands and some sample images to use im my tests
WARNINGS/Disclaimers & Responsibilities
If YOU choose to follow this tutorial, YOU & ONLY YOU are held responsible for any mistakes here on out..
if following the commands and screenies are followed step by step and correctly, you should not have a fail at all, ive now done this to my personal device 6 or 7 times without fail..
My device is ROOTED, Yours should be as well with twrp installed, like a typical tweaker/flashaholic
i DIDNT make a backup because i trust enough in my skills and knowledge to NOT always make a mistake,
when i do make a mistake without a backup i suffer, YOU are responsible for making your own backups if wanted...
the LOGO partition is 16mb in size according to this programs root access information, plenty of play space
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en
DiskInfo Screenshot Sample
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I personally used the original OnePlus drivers that the phone has the built in installer for,
Minimal ADB and Fastboot installer from @shimp208 HERE,
the above mentioned DiskInfo app, and logoInjector.exe from HERE
and believe it or not, MS-Paint & patience
PLUS... most of all, Lots of READING and RESEARCH,
HOW TO
So you want to do this i guess then eh?!
well, lets get on it then
first of all, download and extract to your desired area the op2logoInjector.zip package linked to HERE
Open said *.zip and look at each of the .png's included to decide which you want to edit,
edit them in your preferred image editor to your liking, PLEASE reserve the ORIGINAL filename structure
Once you've finished the edits, simply run the op2logoinjection.bat to inject the files back into the logo.bin
when program finishes, it will produce a file called "modified.logo.bin", take the original "logo.bin" file and rename it to "logo.bin.orig"
take that "modified.logo.bin" file just created and rename it to " logo.bin ",
then proceed to execute the "ADB_Reboot.bat" file to reboot into fastboot mode ** MUST HAVE ADB DEBUGGING ENABLED **
once in fastboot, then proceed to execute the "FastBoot_LOGO_FLASH.bin" to flash your modified logo.bin
if succesful then execute the "Reboot_Device.bat"
Here is a sample of my custom edited logo.bin contents
CREDITS & Thanks
i give ALL credits to the original content owners below, and me for the edits and batch file and testing on personal device..
@makers_mark for the logoInjector.exe and commands,
@oneplus for the device itself and logo.bin and most of image content used,
@shimp208 for the Minimal ADB and FastBoot Installer
AND anyone else whos content i may have used and forgotten to mention, my apologies, please let me know if so!
PLEASE do let me know if there is something i can add or streamline in this process
and DO feel free to share your custom edits here if you like so we can amass a gathering and localize the OP2 logo editing here
reserved #1
Going to be adding some pre-made by me custom logo.bin's here for others to try if they like
Stay Tuned!
RESERVED #2 just in case
Maybe a MOD could possibly STICKY this ??
so it would help all who wish to customize there boot logo's
Isn't this already existed here and I guess @makers_mark is the main author.. Please give proper credits.
Pardon me if I missed any of such credits.
nicesoni_ash said:
Isn't this already existed here and I guess @makers_mark is the main author.. Please give proper credits.
Pardon me if I missed any of such credits.
Click to expand...
Click to collapse
Credits are there to @makers_mark, and permission already granted to use the tool
and yes that @makers_mark has a thread regarding the tool and how to use it,
but there is alot of stuff not explained clearly for some to go ahead and flash stuff like this,
this hopes to help minimize the risk and maximize the experience of customizing your device to your liking easily..
hence the batch scripts and tools and samples all included in a single file double hosted so that others such as myself,
can easily find this thread if interested in modifying ones boot logo's.. is that a fair explanation as to why i posted this ?
Sure mate, I have no issue in an identical but a more thorough and helpful thread. I guess your explanation is enough and if you have the permission from the author itself then all is great in every universe.. Cheers..
No worries, and thanks for the care to make sure a thread is valid and credited properly
good forum etiquette
OP has been edited to clean the code in the credits section so its more clear in the drop down.
* also, the MAIN reason of tutorial post, seeing as the forums for this device dont seem to pertain all this info for
the specific task at hand(boot logo edits) and are fairly new with dev's and contributors, or progress is slow in the forums,
then i feel like id like to provide some of my help
here's my custom boot logo for my op2
My apologies for the delay in bringing out some zips, just switched to a new dell i5 latitude with Linux mint 64bit, getting it all setup and getting used to it..
Finally.. Some progress, my first switch to Linux..
Here's my custom Boot logo
shreyas.kukde said:
Here's my custom Boot logo
Click to expand...
Click to collapse
I loved the shining silver look, mind sharing the psd?
Sent from my "GT-I9300/OP2" powered by Carbon Rom/Blisspop & Boeffla/ak Kernel
Fueled by 7000mAh ZeroLemon Battery
Gets Stuck
So, i did everything and followed the steps perfectly, but when I enter fastboot mode, the programm that is supossed to inject the logo.bin gets stuck and just says waiting for device, any suggestions?
Thanks for the guide, it looks pretty helpful for anyone who wants to do it, as soon as I saw the tools and the name of the partition I skipped the guide since everything else simply already became obvious to me without having to read. I didn't know that nowadays the logos have their own separate partition, back in my days the kernel had them incorporated.
Might make some flashable zips :^).
Sent from my ONE A2003 using Tapatalk
Thanks, here is my custom logo.bin.
http://imgur.com/a/owjU5
One more suggestion to the op. I guess it's better to add in the OP on android version this work and on which this doesn't so no one breaks their devices. I hard bricked my 1+1 once.
Hey !
Thanks man, it worked !
I'm on OOS 3.5.6 !
Here's the one I created.
[ROM][BLU Studio C5+5 D880U & D890U] 100% Factory Stock OS Untouched (D880U EXPOSED!)
Today I'll be providing something that seems to be rather scarce throughout the internet. A perfectly clean, untouched, 100% factory stock rom for the blu c5+5 (both the D880U and D890U). Before we get to that, I'd like to clear up some confusion that has plagued this phone since its inception on the market. The infamous D880U, that seems to not exist every time owners try looking for information on it online, unable to find a ROM or even written support for the device, will be exposed today.
I'm here to tell you that the D880U doesn't exist. It's a scam, created by GSM service providers such as Bmobile, in contract with BLU. These providers wanted to sell the C5+5 in their respective territories (mostly the Caribbean & South America) as a single-sim device. To do this, they'd often cover one of the sim slots with stickers or plastic that fit perfectly so it was flush, and said you'd void your warranty removing that. Then there's the fake reprinted sticker under the battery, which called the phone a D880U, and only provided you with one IMEI number instead of both. This sticker is placed over the original manufactured label on the back.
Some people have already figured out that the D890U ROM works on the D880U. Well that's because the D880U is in fact a D890U. Take a look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now let's peel the sticker back:
As you can see, If you've spent months searching for a D880U ROM, you'll be searching for the rest of your life. Doesn't exist.
There seems to be one single dominant D890U ROM going around the internet. It comes pre-rooted with an outdated version of KingRoot when you flash it onto your phone, which prevented you from installing updates for the phone OTA and even locally, making backups etc as well using custom recoveries such as TWRP often ended in failure as none of the partitions can be modified/wiped for some reason. In short, the ROM is jacked up, and this is the ROM you'll see being offered almost everywhere you go. One spanish-speaking site has the stock ROM, but it requires you to pay $30USD. I am here to finally offer a free, simple solution to your problems. It's a beautiful thing to finally get out there:
Download Link: https://mega.nz/#!iBVzlTiK!7JFuV_tgdb9E55qUAK76yuwxEKMeB_8uZ_K4hO8YR9c
Install using SP Flash Tools. I hope this helps some of you out.
i would like to ask where do you get this rom, i was one of the first ones to provide the stock rom and honestly i would like you to give the credit to the person who upload this rom, there are actually some one else who upload the rom and i think he would agree me havign into account i'm not asking more than just the credit, like you said other sites ask you money to get rom and we're doing this for free
you can confirm my words on this link
https://plus.google.com/u/0/+JORGEADRIANRIOSRODRIGUEZ/posts/a9x6QwgfrFU
jamadz15 said:
i would like to ask where do you get this rom, i was one of the first ones to provide the stock rom and honestly i would like you to give the credit to the person who upload this rom, there are actually some one else who upload the rom and i think he would agree me havign into account i'm not asking more than just the credit, like you said other sites ask you money to get rom and we're doing this for free
you can confirm my words on this link
https://plus.google.com/u/0/+JORGEADRIANRIOSRODRIGUEZ/posts/a9x6QwgfrFU
Click to expand...
Click to collapse
I read the entire post. I've never seen any of those links. I've never even seen that page in my life. I didn't get a rom from anyone there. You really need to stop fussing like a baby over stuff like this. You (can't even read anything over there, it's all in Spanish), didn't create or patent any android stock roms. This is MY link, on MY MEGA account. I AM sharing this rom, not you or any of your friends. How many roms are uploaded daily in different places by different people? Why are you bugging me? I can't believe you're behaving like someone stole your invention. It's a stock ROM..................
Every other replica of this rom on the internet is not as of a result of you, & you do not deserve credit every time it's posted somewhere. You are truly disgusting. Go try to win points somewhere else please.
Need help flashing
I rooted my blu studio c5+5 but then i unrooted using kingroot. Now that i try to use wireless update it says "your system was damaged, wireless update is disabled!". i have determined that i need to flash the rom but how do i do so. all helo wil be appreiciated. Thanks in advanced
Reply
U will need to have stock ROM
.... delet this
it says: no partition found on 2 files: usrdata and uboot, i opened the scatterloading file and it says:
file_name: data.img
wtf, it should said: file_name: userdata.img, you cant do anything right?
also, i copy and paste an old uboot file, i hope i dont mess anything or it will be ur fault!
ASURAPRIEST said:
it says: no partition found on 2 files: usrdata and uboot, i opened the scatterloading file and it says:
file_name: data.img
wtf, it should said: file_name: userdata.img, you cant do anything right?
also, i copy and paste an old uboot file, i hope i dont mess anything or it will be ur fault!
Click to expand...
Click to collapse
lmao. Yeah cuz I was pretty sure my files were flawless. Glad I could help.
So I will tell you a story. I have a zte phone which is not rootable at the moment, I spent 11 months trying and two days ago I found a firmware with fastboot, because zte disables it on purpose. Novadays rooting is often a problem since oems lock everything and don't care, also we can say the same about users, they think that since Android adds functionality it's good to stay unrooted. Let me tell you that is a stupid way of thinking, not only you are accepting to use a phone as guest (also smartphones are so powerful to be considered pcs) but also you are doing it without knowing that oems leave backdoors on it. I really don't understand why people don't care anymore about rooting. I'm so sad. Now I made a discord server where I'm looking for people, devs in particular, but also other people are welcome, and I want to port qu1ckr00t exploit and make also new one, I'm sick of people and oems, I really don't understand is possible to be so dumb? I really don't know...
Yeah, the war against users has escalated.
I think the only way to delay the inevitable is to buy devices with things open at the lowest level.
I rate this on four levels:
Fastboot unlocked, can write most partitions
Fastboot critical unlocked, can write all partitions
Boot ROM and loader software available (e.g. EDL and Firehose for Qualcomm), can read/write all flash
SoC unlocked (e.g. SecureBoot off in Qualcomm), can boot anything
Even if things are open, "progress" means that things always get more complicated and more of a hassle.
Right now I have my cheap/locked/carrier-subsidized phone stock.
I have my Onyx Poke3 ereader Magisk-less rooted and modded.
Renate said:
Yeah, the war against users has escalated.
I think the only way to delay the inevitable is to buy devices with things open at the lowest level.
I rate this on four levels:
Fastboot unlocked, can write most partitions
Fastboot critical unlocked, can write all partitions
Boot ROM and loader software available (e.g. EDL and Firehose for Qualcomm), can read/write all flash
SoC unlocked (e.g. SecureBoot off in Qualcomm), can boot anything
Even if things are open, "progress" means that things always get more complicated and more of a hassle.
Right now I have my cheap/locked/carrier-subsidized phone stock.
I have my Onyx Poke3 ereader Magisk-less rooted and modded.
Click to expand...
Click to collapse
the problerm is that even if i have fastboot without a code to unlock the bootloader is meanigless, people have to make new exploits
Fastboot that requires a code to unlock and no code = No fastboot.
So, on that scale of 1 to 4 you have a 0.
Renate said:
Fastboot that requires a code to unlock and no code = No fastboot.
So, on that scale of 1 to 4 you have a 0.
Click to expand...
Click to collapse
You got the point, I'm in need of some dev who ports qu1ckr00t exploit to armv7l, since I tried some 32 bit version and the exploit was working but it found wrong addresses. But I can't push links here, maybe in private if someone wants to try porting qu1ckr00t using my kernel source. Unfortunately I'm not a dev so would be impossible for me
I'm not that versed in exploits, although I can see that this relies on crashing binder and using entry points in kallsyms.
Can you even see anything here?
Code:
$ cat /proc/kallsyms
cat: /proc/kallsyms: Permission denied
$ echo 0 > /proc/sys/kernel/kptr_restrict
/system/bin/sh: can't create /proc/sys/kernel/kptr_restrict: Permission denied
Do you have your specific (exact) boot.img? It's trivial to extract kallsyms out of that.
Speaking of fastboot. Have you guys seen the fake empty fastboot that Samsung installs on their devices? Samsung deleted the real fastboot and replaced it with a fake one that doesn't even do anything! Samsung did this on purpose to annoy their users
Skorpion96 said:
oems leave backdoors on it
Click to expand...
Click to collapse
Oh now I finally understand the purpose of this fake empty 'fastboot' on all Samsung devices that doesn't even seem to do anything
And then Samsung constantly force selinux enforcing down your throat on all their devices and there's nothing you can do about it even as root unless you hack your kernel. Sounds like fun right?
That's why I prefer Xiaomi devices nowadays. Cheap price, good hardware, easy to unlock (1 week waiting time which is kind of annoying but still somewhat acceptable), easy to root and debloat and customize
I think one of the major hurdles to achieving root nowadays are all these different read-only protection mechanisms which are shoved down our throats... And having selinux constantly enforcing doesn't really help
Speaking of Enforcing : Have you guys ever heard about the fake root?
It looks and feels like real root but it's fake and I can't do anything with it due to selinux constantly enforcing
Click here if you don't believe me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SE Linux is not a problem.
Just write your own policy.
I do. Learn about secilc.
Step 1: Set permissive.
Step 2: Find out where the "denied"s are.
Step 3: Write your own .cil and recompile.
Get your boot.img
Extract kallsyms
Patch sel_write_enforce to just return with 0 in x0
Renate said:
Get your boot.img
Extract kallsyms
Patch sel_write_enforce to just return with 0 in x0
Click to expand...
Click to collapse
That's awesome but if phone can't be unlocked you can't flash that patched boot image
I was just looking at a boot image from lebigmac.
They're always throwing new stuff at us and I like to keep up with it. There was a small wrinkle in there.
I've seen uncompressed kernels, compressed kernels with extractor stubs, GZIP, LZMA. This one had LZ4 compression.
I'm kind of surprised that everyone seems to have still stuck with GZIPed CPIO for ramdisk.
Why not change it and upset everyone for some marginal benefit?
In any case, the strange thing with lebigmac's boot image is that I could extract the kallsyms but all the addresses were zero.
(This has nothing to do /proc/kallsyms or /proc/sys/kernel/kptr_restrict.)
Has anyone seen this before?
Here is the boot.img that @Renate was talking about in case anyone was wondering
It's from an older HTC U11 device that is giving me the fake root issue briefly mentioned above.
This is slightly off-topic though so please feel free to discuss this fake root issue in THIS THREAD instead.
I just thought I'd mention it here hoping that some Android vulnerability experts would chime in with a possible solution to my fake root problem. Thanks!
Did you check if recovery has the same kernel?
Maybe that doesn't have kallsym_addresse zeroed out.
Skorpion96 said:
So I will tell you a story. I have a zte phone which is not rootable at the moment, I spent 11 months trying and two days ago I found a firmware with fastboot, because zte disables it on purpose. Novadays rooting is often a problem since oems lock everything and don't care, also we can say the same about users, they think that since Android adds functionality it's good to stay unrooted. Let me tell you that is a stupid way of thinking, not only you are accepting to use a phone as guest (also smartphones are so powerful to be considered pcs) but also you are doing it without knowing that oems leave backdoors on it. I really don't understand why people don't care anymore about rooting. I'm so sad. Now I made a discord server where I'm looking for people, devs in particular, but also other people are welcome, and I want to port qu1ckr00t exploit and make also new one, I'm sick of people and oems, I really don't understand is possible to be so dumb? I really don't know...
Click to expand...
Click to collapse
What ZTE phone are you attempting to root? If it has a MTK SoC, I'd recommend trying MTKclient. It was able to unlock my ZTE Blade Vantage 2 (yes, a unlocked Verizon phone) and now I've got Magisk and all.
Smu1zel said:
What ZTE phone are you attempting to root? If it has a MTK SoC, I'd recommend trying MTKclient. It was able to unlock my ZTE Blade Vantage 2 (yes, a unlocked Verizon phone) and now I've got Magisk and all.
Click to expand...
Click to collapse
unfortunately is speadtrum